Last modified: 2012-11-03 18:44:38 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 T36539, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34539 - Oversighting an account globally does not remove it from public lists !
Oversighting an account globally does not remove it from public lists !
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CentralAuth (Other open bugs)
unspecified
All All
: High critical with 2 votes (vote)
: MW 1.19 version
Assigned To: Aaron Schulz
:
Depends on:
Blocks: SWMT 31217
  Show dependency treegraph
 
Reported: 2012-02-20 09:36 UTC by Quentinv57
Modified: 2012-11-03 18:44 UTC (History)
9 users (show)

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


Attachments

Description Quentinv57 2012-02-20 09:36:26 UTC
Hello.

There is a real problem with the CentralAuth extension, and especially with the "global oversight" feature.

I noticed in the past that sometimes oversighting an account globally won't remove stuff in the logs on local wikis (mainly newusers, deletion and block log). I noticed that when restoring a global account, the entries that were previously oversighted by CentralAuth are not restored.

But I've never seen things like that. Now, when you oversight an account, it is not removed from [[Special:ListUsers]].

If you want to know exactly the users I'm speaking about, please contact me privately.

That's really something critical, so I think that something should be done to fix the multiple issues with this extension as soon as possible. Thanks by advance.

Quentinv57
Comment 1 Mark A. Hershberger 2012-02-25 18:57:23 UTC
Making a 1.19 blocker since it looks like this is the result of deploying 1.19 to Meta.
Comment 2 Aaron Schulz 2012-02-27 21:49:07 UTC
Local suppression blocks works, so I assume CA is probably not inserting the local suppression blocks on all the wikis, or at least not properly.
Comment 3 Aaron Schulz 2012-02-28 00:59:18 UTC
Is it just Special:ListUsers as far as you know?
Comment 4 Bawolff (Brian Wolff) 2012-02-28 01:03:10 UTC
SpecialBlockList, SpecialActiveusers, ApiQueryUsers, ApiQueryBlocks, and ApiQueryAllUsers all use the same method of filtering, so should probably be double checked.
Comment 5 Aaron Schulz 2012-02-28 01:12:43 UTC
It's everywhere. I already discovered the bug. It seems to have been broken since the block refactoring in 1.17. The local user ID is new longer used in the Block constructor and it tries to get the ID for the *metawiki* user with the name.

I can see blocks for names that should be hidden in the DB, but their ipb_user field is 0, which makes all the JOINs not find them (e.g. ListUsers).
Comment 6 Aaron Schulz 2012-02-28 02:46:06 UTC
Should be fixed in r112563.
Comment 7 Mark A. Hershberger 2012-02-28 18:29:10 UTC
closing.  reopen if it isn't.
Comment 8 Aaron Schulz 2012-02-28 18:31:08 UTC
Note that effected users will need to be reblocked.
Comment 9 Quentinv57 2012-03-02 18:44:57 UTC
Hello. Some of the globally oversighted users are still displayed on the local user lists. I don't know if there's the same thing on some other pages, but please consider this :

https://en.wikipedia.org/w/index.php?title=Special%3AListUsers&username=Sebastian+Mo&group=&limit=50

Thanks by advance
Comment 10 Aaron Schulz 2012-03-02 23:13:48 UTC
(In reply to comment #9)
> Hello. Some of the globally oversighted users are still displayed on the local
> user lists. I don't know if there's the same thing on some other pages, but
> please consider this :
> 
> https://en.wikipedia.org/w/index.php?title=Special%3AListUsers&username=Sebastian+Mo&group=&limit=50
> 
> Thanks by advance

Did you unblock and reblock the user? See comment #8.
Comment 11 Quentinv57 2012-03-03 08:33:18 UTC
Hello,

I unlocked and relocked the user, it still appears in the list.

Should I unoversight and reoversight ?
If so, I'm not really comfortable with this because oversighted stuff will show up on IRC channels and logs unnecessarily.
Isn't there anyway to correct this directly from the database ? This is a technical problem, so I think it should be solved technically.

Regards,
Comment 12 Rob Lanphier 2012-03-06 00:42:09 UTC
Hi Quentinv57, I'm resolving this issue, and referring future log work to bug 34995.  I think that's a manual cleanup exercise that is very different than what is described at the top of this bug.

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


Navigation
Links