[Solved] After install 1.10 module manager error

[jellef]

Upgrade from 1.9.3.4 failed due to incompatible modules. After removing all UDT's and most modules, the upgrade finally succeeded. In the Extensions / Modules screen there is no option to install modules via XML file. The module manager always fails with the error: A problem occurred communicating with the module server. I decided to do a fresh install on my NAS in a clean directory. The installation succeeds, although at step 7 there is no clear indication that the installation het completed succesfully. However, the demo website and the admin interface are working correctly.

Nevertheless, there are still problems with the module manager. Many attempts to view Available Upgrades or Available Modules fail. I checked the Preferences settings and tried various options without result. Also tried with various browsers (Firefox, Safari, Chrome) also after clearing history and cache. Even with the firewall disabled there is no communication.

Then, suddenly, it worked and saw all available upgrades (none at this time) and available modules. After installing one (AskimetCheck) the module appeared under Modules. But the party was over! No more module Manager without errors. I find some simular reports on the forum, but no clues how to solve it. All installed modules should be compatible, I did not add UDT's.

I can install modules by the XML file (with this new installation it works), but I want to be able to update the modules with the manager.

Remote testing is OK:
Test for remote URL (test_remote_url)
fsockopen: Connection ok!
fopen: Connection ok!

What can be wrong???

[calguy1000]

1. Module Manager caches all requests... (including the check to ensure that it can even talk to the server)... it uses filemtime and php time information to do that. The length of time in the cache is a minimum of 1 minute, or the number of minutes you have set in your 'browser cache age' preference in the site preferences. or 60 (one hour), if that isn't set.

So if you are having magical 'it works once, then won't work for a while' issues. I think that you may be running into the cache thing, which may be caused by a timzeone issue, and intermittent connectivity issues.

2. The XML upload form is only visible IF:
a: You have sufficient permission (a member of the admin group would cover this).
b: The permissions on the various directories are set sufficiently.
c: safe mode is disabled.

[jellef]

Calguy, thanks for your response. Issue 2 can be the correct reason. Now with the new installation the user rights are correct and this works.

The main problem is still unsolved. I cleared the websits cache, the browser cache and history, restarted the browser, no result. s there any other way to clear the cache?

[calguy1000]

This message: A problem occurred communicating with the module server

Usually means that ModuleManager could not talk to the ModuleRepository module within 3 Seconds... its a little test we put in for CMSMS 1.10 to ensure that in the case of firewalls, or restrictive servers, or connectivity issues CMSMS would not hang for 2 minutes or more trying to talk to a remote server.

So I would suspect you have a connectivity issue someplacce. When you change the settings, just be sure to clear the CMSMS cache before you test.

[jellef]

Where can I change this timing?

[applejack]

Check you servers error logs after you have tried to load the Module Manager page. It may give you some clues.

[timdebuurman]

Where can I change this timing?

It says this topic is solved in the title.

Was this timing thing the solution?

If so, can anyone tell how to change this timing?

thx