Last modified: 2011-11-08 23:15:41 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 T34198, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 32198 - Suppression of global account causes suppressor's IP to be listed as a blocking admin in local block log
Suppression of global account causes suppressor's IP to be listed as a blocki...
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
CentralAuth (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Aaron Schulz
: platformeng
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-11-04 03:40 UTC by Hazard-SJ
Modified: 2011-11-08 23:15 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Hazard-SJ 2011-11-04 03:40:35 UTC 
Over a week ago, I locked and hid a global account, and in the local block log (not global log!), I saw my IP (not username!) as the blocking administrator. I unhid and everything went back to normal.
Comment 1 Aaron Schulz 2011-11-04 03:56:36 UTC 
Is the IP still there? One what wiki?
Comment 2 Hazard-SJ 2011-11-05 21:38:53 UTC 
When I unsuppressed it, leaving it locked, the IP disappeared from the blocklist. It was on Technologh Hub's Meta Wiki.
Comment 3 Aaron Schulz 2011-11-07 22:45:59 UTC 
(In reply to comment #2)
> When I unsuppressed it, leaving it locked, the IP disappeared from the
> blocklist. It was on Technologh Hub's Meta Wiki.

When did you unblock. The blocker name should be blank for such rows atm. Also, note that only 'oversight' users can see this bug.

I can't deploy the /trunk (r101442) fix for this, as the IPs will come back again. A maintenance script is needed first.
Comment 4 Aaron Schulz 2011-11-08 23:15:41 UTC 
Script ran and fix deployed.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links