Last modified: 2012-12-08 13:17:23 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 T18441, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16441 - [feature requests] "Protection conflicts" like "edit conflicts"
[feature requests] "Protection conflicts" like "edit conflicts"
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
1.14.x
All All
: Low enhancement with 6 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 42854 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-11-23 19:41 UTC by SoWhy
Modified: 2012-12-08 13:17 UTC (History)
5 users (show)

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


Attachments

Description SoWhy 2008-11-23 19:41:00 UTC
I hope I am doing this right, it is my first feature request:

When multiple people try to save a page, the MediaWiki software creates an "edit conflict" window to warn them that the page has just been changed. 
I would like a similar behavior for protections. For example, this page on Wikipedia was protected four times in a row with the same length: http://en.wikipedia.org/w/index.php?title=Special:Log&page=User_talk%3AEast718
So I think the software should output a warning if 1.) the page has been protected while one was on the protection page or 2.) one chose the same protection level that already is applied (e.g. if it's already indef protected, selecting indef protection should generate a warning). 

Regards
SoWhy
Comment 1 Amalthea 2010-10-20 14:51:45 UTC
Personally, I think it should trigger the conflict if the page was touched at all since opening the form because the basis for the action might changed or gone.

It's actually more important that the API offers such a conflict protection. Often a number of such actions are batched, and will be processed based on outdated information. It should allow guarding against such protection/deletion conflicts if the timestamp of the last revision is passed in, just like it does with editing.

It might be prudent to allow overriding the conflict in the webform as well, otherwise Bad People could theoretically prevent protection/deletion of a page through distributed high-frequency editing.
Comment 2 Krinkle 2010-10-20 14:56:38 UTC
I agree with Amalthea.

To make it like "edit":

* If the new settings are equal to the current settings, ignore it (aka "null edit") (with same I mean: same protection and same end date. Duration may differ.)
* If settings are not the same, and between the current time and wpStarttime (time of opening form page) was a 'protect' action on this page, show the new 'protection conflict' page.

--
Krinkle
Comment 3 Alex Monk 2012-12-08 13:17:23 UTC
*** Bug 42854 has been marked as a duplicate of this bug. ***

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


Navigation
Links