Last modified: 2011-04-14 15:12:58 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13333 - Different levels of protection should use different verbs
Different levels of protection should use different verbs
Status: NEW
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-12 16:46 UTC by Random832
Modified: 2011-04-14 15:12 UTC (History)
3 users (show)

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


Attachments

Description Random832 2008-03-12 16:46:22 UTC
In the case of a protection where the highest protection level is "autoconfirmed", the verb that appears in the log and in the pseudo-edit-summary in the article history should be "semi-protected". The current behavior has caused some media confusion recently.
Comment 1 Aaron Schulz 2008-03-12 16:48:00 UTC
Meh, *everything* causes media confusion
Comment 2 Random832 2008-03-12 16:55:39 UTC
I was just mentioning that since it was what prompted me to file this; more clarity is always a good thing, and you have to admit "[edit=autoconfirmed:move=autoconfirmed]" is a pretty obscure code for someone not already intimately familiar with the jargon.
Comment 3 Aaron Schulz 2008-03-12 17:08:50 UTC
Then maybe the "media" can take the two minutes to ask someone what those mean. Of course ... they won't.

Anyway, this would require a message for every combination of edit/move settings (which can also be custom configured).
Comment 4 Random832 2008-03-13 03:39:37 UTC
Also for create settings... but for simple cases you could just have it be based on the max of any protection setting specified.
Comment 5 FT2 2008-03-14 02:38:20 UTC
[edit needs account;move needs sysop;ends 02:11, 28 March 2008 UTC]

There you go.
Comment 6 FT2 2008-03-14 02:42:21 UTC
Granted that the error message will have to say, "Accounts created very recently, within the last few days, may not be able to edit semi-protected pages until the account has been used for a short time."

But we can clarify the difference between "needs account" and "needs autoconfirm" in the error message shown to editors. Most people using the protect logs will understand that "needs account" really means ".. and a few days since creation". 

(Or if precision's needed amend to "needs active account" instead.)

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


Navigation
Links