Last modified: 2014-03-27 03:12:08 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 T38259, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 36259 - No log of a global unlock
No log of a global unlock
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CentralAuth (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-25 22:08 UTC by Snowolf
Modified: 2014-03-27 03:12 UTC (History)
9 users (show)

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


Attachments

Description Snowolf 2012-04-25 22:08:25 UTC
User "No censorship" was locked by steward Bsadowski1 at 19:45, 25 April 2012 (UTC) and unlocked approximately a minute later. No records or log of the unblock exist anywhere. No notification of it was given to the appropriate wikimedia.org IRC channel either.

Relevant links:

https://meta.wikimedia.org/w/index.php?title=Special:CentralAuth&target=No%20censorship

https://meta.wikimedia.org/w/index.php?title=Special%3ALog&type=globalauth&user=&page=User%3ANo+censorship%40global
Comment 1 TyA 2014-03-27 02:56:02 UTC
Has there been anymore instances of this? I just tried it on vagrant, and I'm not able to replicate this, and noticed at https://meta.wikimedia.org/w/index.php?title=Special:CentralAuth&target=%D0%A7%D0%B5%D1%80%D0%BD%D0%BE%D1%81%D0%B5%D0%BB%D1%8C%D1%81%D0%BA%D0%B8%D0%B9 they are correctly appearing as being unlocked.
Comment 2 Ajraddatz 2014-03-27 03:12:08 UTC
No, it's working fine now. On that one there is a second log action two minutes after it which unlocked.

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


Navigation
Links