Please enable the [[mw:Extension:LocalisationUpdate]] extension on Wikimedia Incubator, with automatic updates.
Community discussion was at [[incubator:Incubator:Community_Portal#LocalisationUpdate]] and the only issue is stability, so please enable it when it is stable enough.
Thanks.
Version: unspecified
Severity: enhancement
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | tstarling | T21312 Enable LocalisationUpdate extension on Incubator | |||
| Resolved | tstarling | T20604 update localised messages as soon as possible (LocalisationUpdate ext) | |||
| Resolved | • Catrope | T22774 Enabling LocalisationUpdate vastly increases CPU activity | |||
| Resolved | tstarling | T22773 Localisation cache dependency objects from extensions kill site when extension is disabled |
Suggest WONTFIX. The extension uses hooks to do a DB query on every wfMsg() call, this would be excessively slow. HTTP fetches are done by a cron job. It would be simpler and more efficient to put this in the cron job instead:
find -name \*.i18n.php -or -name Messages\*.php -exec svn up scap
(In reply to comment #2)
Suggest WONTFIX. The extension uses hooks to do a DB query on every wfMsg()
call, this would be excessively slow.
Good point. It should probably hook into message loading and load all (relevant) messages from the DB then. That'd reduce it to one query at initialization and one for every unique wfLoadExtensionMessages() call.
HTTP fetches are done by a cron job. It
would be simpler and more efficient to put this in the cron job instead:find -name \*.i18n.php -or -name Messages\*.php -exec svn up scap
I don't know a lot about this, but from what GerardM told me I understand that the current code only updates messages whose English equivalent hasn't changed (will ask Gerard whether this is correct), so a simple svn up wouldn't work.