Last modified: 2014-10-16 11:00:47 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T54432, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 52432 - Registering an empty or nonexistent messages file breaks the messages cache seemingly indefinitely
Registering an empty or nonexistent messages file breaks the messages cache s...
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
unspecified
All All
: Unprioritized minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-02 00:10 UTC by Mark Holmquist
Modified: 2014-10-16 11:00 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mark Holmquist 2013-08-02 00:10:10 UTC
Steps to reproduce:

1. Pick your favourite extension to break - I like Extension:UploadWizard
2. Change the name of its messages file in the extension's main PHP file - something like "$wgExtensionMessagesFiles['UploadWizard'] = 'LolUploadWizard.i18n.php';", but *do not* create that file.
3. Load a page that uses the message(s) in that message file - like Special:UploadWizard
4. Note the error. Expected behaviour.
5. Copy the actual messages file to the filename you made up, e.g. "cp UploadWizard.i18n.php LolUploadWizard.i18n.php"
6. Reload the page from step 3 - note that the error is gone, but no messages load
7. Refresh as much as you'd like. Rebuild the message and l10n caches if you want. Hilariously ineffective.
8. Change the name back in the PHP file and refresh the page. Tada. You could alternatively change it to a different nonexistent filename, refresh the page once, and then change it back to a proper name, and refresh it again. The change of filename causes the refresh.

This is probably some overly clever feature that I'm misreading, but it means that if I forget to create an i18n file at first, I'll mysteriously not have messages load on the site. Which causes a bit of confusion. Some better handling somewhere might be good.
Comment 1 Nemo 2013-08-02 06:05:37 UTC
Last time we had a problem like this, IIRC it was due to timestamps of the file? have you tried touch'ing it?
Comment 2 Niklas Laxström 2014-10-16 11:00:47 UTC
I'm unable to reproduce with json i18n.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links