Last modified: 2009-10-01 18:38:24 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 20927 - Checkboxes for RevDelete on user contribs and log pages
Checkboxes for RevDelete on user contribs and log pages
Status: RESOLVED DUPLICATE of bug 20189
Product: MediaWiki
Classification: Unclassified
Revision deletion (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Aaron Schulz
Depends on:
  Show dependency treegraph
Reported: 2009-10-01 17:19 UTC by FT2
Modified: 2009-10-01 18:38 UTC (History)
0 users

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


Description FT2 2009-10-01 17:19:08 UTC
The RevDelete checkbox functionality on page history has proven useful.

But in many cases a vandal will post problematic material with one edit for each of many pages, or across many page move log entries. In many cases one gets a single account with many vandalistic edits. The oversighter cannot select them all and choose to suppress; he/she has to click through on each item and then configure RevDelete for each item. 

Can the checkbox functionality be added to user contribs, deleted contribs, and log pages, so that oversighters can redact entries based on the vandal's contributions page, deleted contributions, or a move log?

(Deleted page history already has checkboxes, but they aren't linked to RevDelete, that would also be useful)
Comment 1 Aaron Schulz 2009-10-01 18:38:24 UTC

*** This bug has been marked as a duplicate of bug 20189 ***

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