Last modified: 2008-08-04 21:06:31 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 T17022, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 15022 - ?action=unprotect should default on (default) and not the current protection level
?action=unprotect should default on (default) and not the current protection ...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-03 08:32 UTC by charitwo
Modified: 2008-08-04 21:06 UTC (History)
0 users

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


Attachments

Description charitwo 2008-08-03 08:32:54 UTC
Seeing as how there's both an action=protect and action=protect, it's kind of silly since they both essentially do the same thing, regardless of which one you are on, the settings bar is always on the current protection level.

If you choose action=protect, it should stay on the current protection level like it already does, obviously so you can choose which level and settings you want.

What should change is... If you choose action=unprotect, the settings level should default to (default) on both sides. Otherwise this action is both redundant and meaningless.
Comment 1 Brion Vibber 2008-08-04 21:06:31 UTC
action=unprotect is obsolete, a holdover from when it was a simple binary action. Now 'protect' and 'unprotect' do the same thing, which is to take you to the protection tab which gives you the details of the protection settings for the page and the ability to change them.

If visiting this tab changed the values, it would be much harder to tell what's going on.

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


Navigation
Links