Last modified: 2007-10-16 09:24:42 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 T13343, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 11343 - Undelete succeeds during database lock
Undelete succeeds during database lock
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-14 21:16 UTC by Brion Vibber
Modified: 2007-10-16 09:24 UTC (History)
3 users (show)

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


Attachments

Description Brion Vibber 2007-09-14 21:16:40 UTC
As reported on my userpage; need to test this.
Comment 1 Prodego 2007-10-16 02:11:39 UTC
Testing this on amidaniel.com (which is rather unstable, but I don't have a local wiki handy), I found that I could actually *successfully* undelete a page during a database lock (it was locked using Special:Lockdb in this case, but I assume anything short of setting the database to read only will have this problem). I would also assume that this is the reason it failed on the Wikipedia server, the server itself was locked. If someone would care to confirm this on a vanilla instillation. 
Comment 2 Roan Kattouw 2007-10-16 08:12:46 UTC
AFAIK, locking the database by setting $wgReadOnly does yield an error message.
Comment 3 Daniel Cannon (AmiDaniel) 2007-10-16 08:42:29 UTC
Confirmed on vanilla install. If the db is locked, when you access Special:Undelete, you will not get the Undelete button. But if the db is locked while undeleting a page, it will succeed.
Comment 4 Daniel Cannon (AmiDaniel) 2007-10-16 09:24:42 UTC
Committed fix in r26768.

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


Navigation
Links