The status report page and admin / config page are not working when module installed.

It works when deactivating the module.

Is there a timeout for the retrieval of update information ?

Comments

sutharsan’s picture

Status: Active » Postponed (maintainer needs more info)

Please specify (URL) which report page and config page. Those of the Localisation Update module, status module or other?
In manually updating the translation status information, there is no delay. It starts when you press the update button. What do you mean with time out?
This behaviour is unknown to me and not reported before. It is possibly caused by you specific server situation/configuration/access. Can this be caused by other modules? does the Update module work correctly?

Avorathol’s picture

Status: Postponed (maintainer needs more info) » Active

Actually, page "../admin/config" is loading some time and then go time out (loading stop because execution time is too long), leaving just a blank page.
Some other pages have the same problem (like "../admin/config/regional/translate/update").

And just disabling Localization update module fix this problem.

Avorathol’s picture

After some tests, another fix : disabling useless languages in "admin/config/regional/translate". With just english and french I don't have this problem anymore.

I think it's a problem of translate files size, linked to http://drupal.org/node/569004 . So maybe a duplicate bug ?

sutharsan’s picture

Status: Active » Closed (duplicate)
frederickjh’s picture

Hi!

I believe that the wrong issue is reference as the duplicate in the last post. It should be #569004: Add support for seek based batch import of .po files which was mentioned in the post previous to it.

God Bless!
Frederick

sabotagenl’s picture

I had this too. When i updated to the latest DEV version, the problem was solved! :)

Chimos’s picture

Issue summary: View changes

I had this issue on a fresh clone of a website. The clone showed "unexpected error. Come back later..." only in URLs: .../admin/config and .../admin/reports/status and some other.

The problem was my backup SQL export being uncomplete for some reason, the three last tables were not included. Exporting only those tables and importing them in the clone fixed the issue.