Hi,

Today I experience something strange. My /admin/config-page was impossible to get to. After much hassle, I tracked it down to system_check(), and via that to l10n_update_requirements() and via that to l10n_update_http_request().

The reason of course is that ftp.drupal.org is currently down. This leads to a 30-second timeout for each and every module installed. Or in layman's terms: You'll give up loading the page long before all the timeouts are reached.

So, would it be possible to have some sort of check, where if a single timeout was experienced, all other checks was aborted?

Regards
Morten

Comments

rvilar’s picture

I experienced the same. How can we improve this? A global timeout or failing all requests when one of them get a timeout?

gábor hojtsy’s picture

I agree this would be a great improvement.

Cyclodex’s picture

Arg, today I moved my first Drupal project online. Everything worked, but not the config page...
And I am fighting the whole day to find whats going on. The funny thing is, that only happens when I clear the cache and then moved to the config page, before It worked without problems... (and of course when you put a site online you have to clear cache)
(that behavior was nicely test-able with my backups)
With disabling a group of modules and retry after clear-cache i finally got to the localization update module. Now I searched for bugs, and found this thread... phew... ;) Disabling this module for the moment, fixes the problem...

djg_tram’s picture

Gábor, not only an improvement but it's absolutely required. :-) No matter how good the module is, I had to switch it off on all my sites because of this issue. Is there any current work on this or shall I go for a patch (time permitting, of course, the usual biggest bottleneck)?

gábor hojtsy’s picture

Yes, a patch would be great, so we can get people test it and get it committed! Thanks!

sutharsan’s picture

Issue summary: View changes

Drupal core's drupal_http_request() now has an option to set the time-out. Can someone port this to l10n_update, while maintaining the ability of l10n_update_http_request() to be used at installation?

sutharsan’s picture

Status: Active » Closed (won't fix)

No activity, no support. Closing the issue.