Closed (fixed)
Project:
Localization server
Version:
6.x-2.x-dev
Component:
Database
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Mar 2010 at 20:44 UTC
Updated:
2 Apr 2010 at 00:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
gábor hojtsyHm, agreed, looks buggy. I'll need to grab a copy of the DB and experiment with this locally.
Comment #2
gábor hojtsyActually, I looked at the live DB to diagnose this quicker. Compared the suggestion and translation flags. Thankfully, all this data is just caching of values from the translation table, so if its broken, we can regenerate.
So looks like flags were ok for suggestions (at least looking at the numbers) but not at all ok for translations (look there is a 10000 gap there). This got me thinking that the flag initialization code was at fault (this is too big of a difference to appear in one day).
So looked at the update code, and indeed, it is dropping the empty translation placeholders used previously, before calculating which strings had translations. So where empty placeholders existed before, it thought those have translations. To fix this quickly on the live DB, I sent the site to maintenance, dropped the flags and recreated them with the same code used in the update function.
Then checked your links, and they seemed to work fine, so brought the site back into operation.
Finally, for others updating the module, I've reordered the code so they'll have good data at the start. Committing this to the l10n_server module.
So all-in-all the live server should run on fine data, and the updates should get an older server to the right state. Thanks for the report.
Comment #3
linulo commentedI used the LocServ extensively and did not encounter any problems regarding this issue anymore.
Thank you very much for the quick action.