Page MenuHomePhabricator

Enhance Blocking and tagging from checkuser interface: add new page
Open, MediumPublic


Author: lar

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?

From T145340#2627061 @Legoktm wrote:
The mass block CheckUser interface should be split to a separate special page.

We could still display the form on the CheckUser results page, however, it would POST to a different special page.

The special page could then be enhanced to support further blocking options like T24120: Enhance Blocking and tagging from checkuser interface: add dropdowns.

Also, separating it from CU permissions would enable us to open it up to all administrators (and possibly move it out of CU?).



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:58 PM
bzimport added a project: CheckUser.
bzimport set Reference to bz22119.
bzimport added a subscriber: Unknown Object (MLST).
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 27 2015, 4:58 PM
Krenair added a subscriber: Krenair.Feb 7 2016, 6:49 AM

You could use JS to set the form's target to _blank... But for the server to try to remember what the results of the user's last query were and spit back out the same, I guess we'd have to do some ugly storage in session/memc. :/

Restricted Application added a subscriber: JEumerus. · View Herald TranscriptFeb 7 2016, 6:49 AM
Glaisher updated the task description. (Show Details)Sep 12 2016, 9:05 AM
Glaisher claimed this task.Sep 15 2016, 9:29 AM
Aklapper removed Glaisher as the assignee of this task.Jun 19 2020, 4:27 PM
Aklapper added a subscriber: Glaisher.

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)