Just found an odd problem -- not sure if it's something I did or if it's just screwed up in general though.
Noticed that a scap was recently done on Wikimedia and so went to try out Special:Blockip to find that the "Prevent user from sending e-mail" message (MediaWiki:Ipblockemail) displayed as <ipblockemail> (or whatever screwiness it is when there is no such message), although the message had been defined in MessagesEn.php. When I went to the system message, it displayed the correct default message but did not take effect until I saved the message (creating it with its default value). This problem does not seem to exist on testwiki, and it never did on my local wiki or my public testwiki. Any idea what's going on?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Daniel Cannon wrote:
Noticed that a scap was recently done on Wikimedia and so went to try out Special:Blockip to find that the "Prevent user from sending e-mail" message (MediaWiki:Ipblockemail) displayed as <ipblockemail> (or whatever screwiness it is when there is no such message), although the message had been defined in MessagesEn.php. When I went to the system message, it displayed the correct default message but did not take effect until I saved the message (creating it with its default value). This problem does not seem to exist on testwiki, and it never did on my local wiki or my public testwiki. Any idea what's going on?
This is an artifact of the caching system we use for message files. You should be able to reproduce it via something like this:
1) Go into $IP/serialized
2) Run "make" to build serialized cache files of all the message arrays
3) Add a new message to the message files and make the software use it
Assuming I'm not off my rocker, this'll show the behavior you describe. ;)
When making updates, you have to update the serialized files by running "make" in there again; then the message will show up.
Now, the serialization update is a part of the scap process, so you _shouldn't_ actually see this problem on the live site unless you're playing on test.wikipedia.org between a "svn up" and a scap. There might be race conditions though if it's not copying the serialized files before the code, or other such intermittent boondoggles.
- -- brion vibber (brion @ wikimedia.org)
On 6/12/07, Brion Vibber brion@wikimedia.org wrote:
This is an artifact of the caching system we use for message files. You
I figured as much.
should be able to reproduce it via something like this:
Go into $IP/serialized
Run "make" to build serialized cache files of all the message arrays
Add a new message to the message files and make the software use it
Assuming I'm not off my rocker, this'll show the behavior you describe. ;)
Nah, I'll take your word for it :D.
When making updates, you have to update the serialized files by running
"make" in there again; then the message will show up.
Now, the serialization update is a part of the scap process, so you _shouldn't_ actually see this problem on the live site unless you're playing on test.wikipedia.org between a "svn up" and a scap. There might be race conditions though if it's not copying the serialized files before the code, or other such intermittent boondoggles.
Hmm .. well, it was on enwiki, not testwiki. Judging by the server logs, it's quite possible that I did this right while you were in the middle of the scap (though I'd note that you didn't log the actual scap :P). In any case, it gave me a bit of a scare when I first saw that, thinking all of the wikis might have gotten screwed up as the result of a typo or the like, but it all seems to be working now on all of them.
Thanks for your reply.
wikitech-l@lists.wikimedia.org