Last modified: 2013-12-15 02:32:39 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 T24890, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 22890 - Checkuser mass blocker does not affect already blocked users
Checkuser mass blocker does not affect already blocked users
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: SWMT
  Show dependency treegraph
Reported: 2010-03-19 00:13 UTC by Hersfold
Modified: 2013-12-15 02:32 UTC (History)
3 users (show)

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


Description Hersfold 2010-03-19 00:13:20 UTC
To duplicate:

1. Block an account (settings on the block don't matter)
2. Checkuser the account's IP address with "IP to users"
3. Check the box next to the account's name
4. Enter a block reason into the "block selected users" form at the bottom of the page
5. Click "Block selected users"

The form will replace the content of the account's user and user talk pages as requested and expected, but the original block will not be replaced with the ACB-Autoblock-indefinite block that is expected from the form.
Comment 1 Hersfold 2010-03-20 03:31:01 UTC
After some discussion on the checkuser list, it sounds as though this may be intentional; I'd still like to see this changed to overwrite existing blocks, or at least provide an option to override existing blocks (similar to bug 16306). Because of this, I've changed the severity to "enhancement". Changing the extension to handle existing blocks in this manner would mirror the current behavior of Special:Block, which will replace existing blocks with the new settings; I would assume that this is what most checkusers would expect to happen now.
Comment 2 Bugmeister Bot 2011-08-19 19:12:19 UTC
Unassigning default assignments.

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