Last modified: 2007-01-19 18:27:49 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 8700 - Administrators' revert function reverted to different article after rw re-enabled for db
Administrators' revert function reverted to different article after rw re-ena...
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-01-19 14:57 UTC by Alex Nordstrom
Modified: 2007-01-19 18:27 UTC (History)
0 users

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


Description Alex Nordstrom 2007-01-19 14:57:13 UTC
After the Wikipedia database was read-only for several hours and was made
writable again, I attempted to revert several diffs which I had loaded before
the outage. Because of a loss of session data, I first had to reload the diffs,
after which I hit revert. All reverts went as expected, except for one:

As you can see, instead of being reverted, the article was replaced by the
contents of another article which I reverted at the time:

Curiously, while the incorrectly reverted page appeared in the diffs and in edit
mode, I was seeing the right version when viewing the article despite a hard
Comment 1 Brion Vibber 2007-01-19 18:27:49 UTC
This is a caching artifact due to the database oddity after recovery.
I've manually cleared the diff cache for this edit.

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