Last modified: 2009-05-17 17:33:37 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 T20466, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18466 - Admins should see a warning when in process of overruling a move protection
Admins should see a warning when in process of overruling a move protection
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-14 20:11 UTC by pgrawehr
Modified: 2009-05-17 17:33 UTC (History)
3 users (show)

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


Attachments
Adds a move protection warning to Special:Movepage (2.42 KB, patch)
2009-05-03 02:24 UTC, Nakon
Details

Description pgrawehr 2009-04-14 20:11:53 UTC
When an user attempts to edit a page that is semi-protected (or an admin attempts to edit one that is either semi- or full-protected) he get's a message box with a warning and the current block reason. Especially as an admin this is really important since overruling the block could be considered abuse of sysop rights. A similar message should pop up if an admin attempts to move a page that is move-protected. Except if looking into the logs, he has no way of knowing that he would just overrule a full move-protection.
Comment 1 Nakon 2009-05-03 02:24:11 UTC
Created attachment 6081 [details]
Adds a move protection warning to Special:Movepage

patch included.
Comment 2 pgrawehr 2009-05-04 18:52:43 UTC
Looks ok. Just a remark about practical issues: On most wikimedia-wikis, only logged in (and autoconfirmed) users can move pages anyway. In such a case, would we just remove (=empty) the semi-protected warning (because it's just confusing). What would you suggest?
Comment 3 Siebrand Mazeland 2009-05-17 17:33:37 UTC
Applied with minor tweaks in r50701. Thanks.

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


Navigation
Links