Last modified: 2011-03-13 18:06:16 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 T10817, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8817 - Prevent double protection of pages, as with blocking
Prevent double protection of pages, as with blocking
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Lowest enhancement with 4 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://de.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-29 00:27 UTC by Thomas Goldammer
Modified: 2011-03-13 18:06 UTC (History)
1 user (show)

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


Attachments

Description Thomas Goldammer 2007-01-29 00:27:14 UTC
As can be seen under the above URL, this page was blocked twice with different expiring date. (I 
wonder which one is than the valid one.) I think it would be great to get an error message if the 
page is already on the same block value (thus edit=autoconfirmed, move=autoconfirmed in that 
example above). I mean a similar anti-editconflict feature as was programmed for the user 
blocking. If this bug has been reported already, please tell me where on my meta user page. I 
didn't find it.
Comment 1 bdk 2007-07-23 19:04:50 UTC
The same is for multiple unprotections, see e.g. http://de.wikipedia.org/w/index.php?title=Spezial%3ALogbuch&type=protect&user=&page=Diskussion%3AHom%C3%B6opathie on 23 July, 2007. 
Comment 2 Aaron Schulz 2008-09-05 22:52:31 UTC
This would just make changing protection more of a pain. It would be nice if blocking did auto-overriding.

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


Navigation
Links