Last modified: 2008-09-07 01:12:00 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 10799 - Provide a list of predefined reasons in the protection form
Provide a list of predefined reasons in the protection form
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-04 09:26 UTC by achates
Modified: 2008-09-07 01:12 UTC (History)
3 users (show)

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


Attachments

Description achates 2007-08-04 09:26:07 UTC
Please implement a dropdown box with predefined reasons for deleting and protecting pages similar to the Dropdown-Box with predefined Block-Reasons. Admins sometimes give somewhat sloppy Deletion-Reasons, which may upset the Author of the deleted Page.
Comment 1 Rob Church 2007-08-04 12:00:05 UTC
Refactoring to handle just the protection issue; bug 9633 handles predefined deletion reasons. I'm not sure we need such a list for protection, since a lot of protection issues will require a more thorough explanation, so I'm less inclined to think it a good idea to support a bunch of boilerplates.
Comment 2 Brion Vibber 2007-11-26 16:00:23 UTC
I suspect a lot of cases are going to be fairly generic -- 'protecting for X hours in response to edit war' etc.

It might be suitable to allow a combination of both a drop-down boilerplate and a custom comment to clarify. Or that might be crazy talk, dunno. :D
Comment 3 Mike.lifeguard 2008-02-08 01:58:08 UTC
Having both a combo box and text box is exactly what we have currently for deletion and blocking; why should this be any different?
Comment 4 Aaron Schulz 2008-09-06 23:23:37 UTC
Done in r40555
Comment 5 Lejonel 2008-09-07 00:56:50 UTC
I think the messages for "other expiry" and "other/additional reason" should be split into two messages for the labels and two messages for the options. for consistency with other labels, the labels should have colons and be capitalised. While the options should not have colons, and at least the other expiry time option should not be capitalised.
Comment 6 Aaron Schulz 2008-09-07 01:12:00 UTC
(In reply to comment #5)
> I think the messages for "other expiry" and "other/additional reason" should be
> split into two messages for the labels and two messages for the options. for
> consistency with other labels, the labels should have colons and be
> capitalised. While the options should not have colons, and at least the other
> expiry time option should not be capitalised.
> 

Didn't even notice. Done in r40561.

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


Navigation
Links