Closed (duplicate)
Project:
Localization update
Version:
7.x-1.0-beta3
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jun 2012 at 09:54 UTC
Updated:
29 Apr 2018 at 09:22 UTC
Jump to comment: Most recent
Comments
Comment #1
sutharsan commentedPlease 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?
Comment #2
Avorathol commentedActually, 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.
Comment #3
Avorathol commentedAfter 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 ?
Comment #4
sutharsan commentedAgree. Duplicate of #560994: README.txt in module description should be linked to the actual file
Comment #5
frederickjhHi!
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
Comment #6
sabotagenl commentedI had this too. When i updated to the latest DEV version, the problem was solved! :)
Comment #7
Chimos commentedI had this issue on a fresh clone of a website. The clone showed "unexpected error. Come back later..." only in URLs:
.../admin/configand.../admin/reports/statusand 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.