Follow-up question to TIM STARLING:
you kindly answered me about 10 days - I have one additional question, see at the END
Thomas Gries wrote:
> (1) Is there a simple way to bulk copy (clone) the whole
> MediaWiki:namespace from one wiki to another wiki (on the same server) ?
Yes, there's maintenance/dumpMessages.php. Pass the resulting file as a
parameter to maintenance/rebuildMessages.php. The other option is to use
SQL, e.g. SELECT INTO OUTFILE.
> (2) Is there a simply way to extract let's say five MediaWiki:pages so
> that I can put it together with a patch into the CVS ?
> In my case, the coming e-mail notification patch for 1.3.2 (see my
> recent (pre)documentation pages on the MetaWiki) uses a couple of
> MediaWiki:namespace pages for composing the notification mails and other
> purposes and I want to publish these important pages together with the
> program patch in one "package".
>
> But I don't know, how.
Language.php is the canonical location for message text, not the
MediaWiki namespace. The namespace will be automatically initialised
from the language file by the installer, for new wikis. Copy your
default message text into Language.php and create a patch in the usual way.
-- Tim Starling
Applying my patch needs to add let's say 2 messages. How can this be done automatically, I mean, a sysop can patch files
Skin.php (for example) and Language.php (with the new 2 messages) as proposed by you - see above, but ....
Question:
... when (how) are these changes in Language.php reflected in the running wiki? In other words: the change in Skin.php is effective immediately, but when(how) will the change in Language.php be effective (e.g. "copied" to the MediaWiki:namespace) ?
My program patch uses for example a call to wfMsg('EmailnotificationMessage1') and wfMsg('EmailnotificationMessage2')
Tom