Extension talk:LocalisationUpdate/Archive 1

Some comments
+siebrand> LocalisationUpdate.php should be smaller, and you should lazy load from class files. +Nikerabbit> the sql should probably be hooked to LoadExtensionSchemaUpdates, it doesn't seem to support table prefixes +Nikerabbit> I also don't like that it creates a new entry point, either write a command line scripts, a special page or both +Nikerabbit> how does it determine which updates are compatible and which are not? +Nikerabbit> $query = "select value from localisation where identifier = '".$db->strencode($lckey)."' and language = '".$db->strencode($langcode)."'"; +Nikerabbit> we have nice $db->select for this :) +Nikerabbit> I also see some code duplication there – Nikerabbit 07:25, 20 May 2009 (UTC)

update database
Thanks, GerardM 22:27, 20 May 2009 (UTC)
 * when a message is changed or removed from the local messagefile (in English) will the localisation be removed from the database ?
 * when a message is changed in SVN, will the localisation be saved for as long as the local message has not changed ?

two issues left
I have been asked by Naoko to write the two issues that need some more work. Thanks, GerardM 07:53, 22 July 2009 (UTC)
 * The performance of the software took a hit when some work was done to make the software more safe.
 * Tom's plan is to talk to Brion and ask for his advise
 * When a language known in the Names.php is new to the localisation of an extension, it needs to be introduced in the database.

Get errors when run update script
When I ran  on the command line, I got the following errors:

PHP Catchable fatal error: Argument 4 passed to LocalisationUpdate::compareFiles must be an array, boolean given, called in /srv/www/w.ray.io/public_html/extensions/LocalisationUpdate/LocalisationUpdate.class.php on line 163 and defined in /srv/www/w.ray.io/public_html/extensions/LocalisationUpdate/LocalisationUpdate.class.php on line 305

--Sparanoid 07:44, 12 September 2011 (UTC)

Assistance needed: LocalisationUpdate on a wiki family
I recently did a major transition from standalone MW installations to shared resources ones. I have 7 wikis so it took me a lot of time to administer them all, plus, they took a lot of space. Since they are all in the same server I did a "Scenario 4" setup. First I updated all to most recent MW version (1.21.2). Then I created a separate dir called "common" and put there all extensions from all wikis (each one has a different compilation of extensions; they are not a real family, just some wikis in the same server). In the same dir I also put the bin, docs, includes, languages, maintenance, resourses, skins and tests dirs. Then I created symbolic links for all the moved dirs. For example, in /wiki1/wiki/ I have deleted extensions dir and created a symbolic link called "extensions" that points to /common/extensions. And so on. This approach saved me 2 Gb of space and 50$/year. But now I don't know what will happen if I run LocalisationUpdate because I am not sure how it works and I am also not very familiar with linux.

My guess is that LU will run with no issues. My guess is that it will try to update, for example, the "Poem" extension so it will try to update files inside wiki/extensions/Poem dir but through the symbolic link it will go to common/extensions/Poem and update those files there instead. And it will do this for all files in wiki1. Then, in wiki2, it will go again to common/extensions/Poem dir only to find that these files are updated so it will skip them and update only wiki2 extensions that don't exist in wiki1. And so on.

Can someone please confirm (or invalidate) my reasoning? All wikis are live and I don't want to conduct experiments on them. And if this way described above is wrong, then what is the proper way to use LU with a wiki family? I know that the Wikimedia family has a much more complicated setup than the one described above and still uses LU to update. So how can this be done?

P.S.: The funny thing is that just a few days ago I had just finished creating cron jobs with LU so as all wiki messages be up to date every day!

P.S.2: LU is essensial to me since I am a very active translator in translatewiki and I proofread and correct messages all the time.

--Ioannis Protonotarios 12:16, 14 September 2013 (UTC)

In 1.21.2 blocks wiki
I have just installed 1.21.2 with Extension:LocalisationUpdate. Note that the wiki will not start. When removed from core the wiki works properly again.--Juandev (talk) 14:41, 19 October 2013 (UTC)


 * This is a known bug (it has been discussed in Bug 46885 - Fatal error after installation when using LocalisationUpdate). The problem is that the MW installer does not do the proper configuration of LU extension. The solution is to add the cache dir below the require_once like this:


 * After that it will work (at least once)! But then you may find that the 1.21.2 bundled LU version is problematic. Some days later you may not get any more localisation updates. I don't know why this happens. Just install latest version/update of extension LU (i.e. remove LU folder and pull a new one from git) and from that point on it will work perfectly every time! (I suggest to install latest version anyway)


 * --Ioannis Protonotarios 18:38, 19 October 2013 (UTC)

This seems to be reported also here: Thread:Project:Support desk/Fatal exception of type MWException after install MW from 1.21.0