Last modified: 2009-03-10 03:57:10 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 T19833, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 17833 - "Hide username from the block log, active block list and user list" removes users from CU results
"Hide username from the block log, active block list and user list" removes u...
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
CheckUser (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Aaron Schulz
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-07 04:56 UTC by Mike.lifeguard
Modified: 2009-03-10 03:57 UTC (History)
1 user (show)

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


Attachments

Description Mike.lifeguard 2009-03-07 04:56:55 UTC
After a user is blocked with the "Hide username from the block log, active block list and user list" option on, they no longer appear in CU results. This should certainly *not* be the case, as our most disruptive users are blocked with that option - the exact same users we are most likely to need CU data for.
Comment 1 Aaron Schulz 2009-03-07 06:25:21 UTC
The offending user's edits and log entries should still be there. Is there an example of this?
Comment 2 Mike.lifeguard 2009-03-07 21:54:18 UTC
(In reply to comment #1)
> The offending user's edits and log entries should still be there. Is there an
> example of this?
> 

There was one last night (how I figured this out), but I can't recall which one it is, and there are too many accounts spread over too many wikis to figure out which is was without a serious investment of time and energy. I'll perhaps do a test on testwiki.
Comment 3 Aaron Schulz 2009-03-08 05:41:04 UTC
Is the issue just the "user is blocked" notice? Fixed that in r48155.
Comment 4 Mike.lifeguard 2009-03-08 05:43:17 UTC
(In reply to comment #3)
> Is the issue just the "user is blocked" notice? Fixed that in r48155.
> 

No, I blocked the user then ran a CU & got no results at all - not even the account creation. After that, did CU before blocking.
Comment 5 Aaron Schulz 2009-03-08 05:48:38 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > Is the issue just the "user is blocked" notice? Fixed that in r48155.
> > 
> 
> No, I blocked the user then ran a CU & got no results at all - not even the
> account creation. After that, did CU before blocking.
> 

This doesn't seem related to the block option.
Comment 6 Mike.lifeguard 2009-03-10 03:57:10 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > Is the issue just the "user is blocked" notice? Fixed that in r48155.
> > > 
> > 
> > No, I blocked the user then ran a CU & got no results at all - not even the
> > account creation. After that, did CU before blocking.
> > 
> 
> This doesn't seem related to the block option.
> 

You're right, I can't replicate this. Marked as WORKSFORME & I'll see if I can figure out what this really was.

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


Navigation
Links