Last modified: 2013-04-21 18:02:48 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 T24119, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 22119 - Enhance Blocking and tagging from checkuser interface: add new page
Enhance Blocking and tagging from checkuser interface: add new page
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 12808
Blocks: SWMT
  Show dependency treegraph
Reported: 2010-01-16 15:09 UTC by Larry Pieniazek
Modified: 2013-04-21 18:02 UTC (History)
3 users (show)

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


Description Larry Pieniazek 2010-01-16 15:09:27 UTC
The enhancement to Special:Checkuser to allow blocking from the returned results page done in 12808 ( is hugely useful, for prolific sockmasters it saves a great deal of time and it's generally awesome. However I have two enhancement requests which I will enter as separate bugzilla entries.

The first one is that often, there is a desire to do further investigation, even if it is clear that the accounts found need blocking. The "block selected users" button carries out the block on the same page that the results were presented on, losing the results found so that it can display the text "the users X Y Z were blocked". It would be nice if there was a way to request the block be performed, but launch the result onto a new page instead of on the same page. While you can use the "back" button to return to the previous page this is not always optimal. Perhaps a check box to ask for a new page or something similar? Perhaps a change in default behavior?

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