Last modified: 2009-01-02 11:56:11 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10536 - MediaWiki namespace message caching seems to ignore page moves
MediaWiki namespace message caching seems to ignore page moves
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Low trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-07-11 06:57 UTC by Nick Jenkins
Modified: 2009-01-02 11:56 UTC (History)
2 users (show)

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


Description Nick Jenkins 2007-07-11 06:57:35 UTC
Steps to reproduce are below. Unexpected behaviour occurs in step 5:

Step 1: Create a message at [[MediaWiki:foo]] that says "this is a test".
Step 2: To the end of /index.php, add: print '<h2>' . wfMsg( 'bar' ) . "</h2>\n";
Step 3: View a page on the wiki. The footer of the page now contains "<bar>", as expected.
Step 4: Move [[MediaWiki:foo]] to [[MediaWiki:bar]], and then view another page on the wiki.
Step 5: What happens: The footer of the page still contains "<bar>". Would now expect the footer of the page to contain "this is a test".
Step 6: Edit [[MediaWiki:bar]], no need to make any changes, and then save (i.e. make a null edit).
Step 7: What happens: The footer of the page contains "this is a test", as expected.

Conclusion: There is caching of MediaWiki namespace messages occurring, but that caching does not get invalidated or refreshed on page moves, even when those page moves directly affect messages that are displayed to the user.
Comment 1 Joshua C. Lerner 2008-07-21 14:50:27 UTC
I've run into this a couple of times.
Comment 2 Aaron Schulz 2009-01-02 11:03:15 UTC
Should be fixed by r28690
Comment 3 Gurch 2009-01-02 11:56:11 UTC
Just tried it with r45314 and it does indeed seem to be fixed

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