Last modified: 2010-05-15 15:33:03 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 1184 - expiry time of indefinite blocks shown as the current time
expiry time of indefinite blocks shown as the current time
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2004-12-24 01:15 UTC by wiki_tomos
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Description wiki_tomos 2004-12-24 01:15:13 UTC
This is from Japanese Wikipedia's bug report page. 

The Special:Ipblocklist shows that indefinitely blocked IPs are shown to be
blocked not until "indefinite." Instead it is shown to be blocked until the
current time - the very moment a viewer takes a look at the log. 

Pointed out by ja:User:PiaCarrot, replicated by me.
Comment 1 PiaCarrot 2004-12-24 13:12:07 UTC
Additional cases:
Expiry time of IPs blocked recently(after version-up) is
shown until the time when sysop blocked the IPs.
Comment 2 Brion Vibber 2005-01-11 09:28:19 UTC

Interaction between this bug and the fix for bug 1204 may have resulted in 
incorrect automatic unblocking of some indefinite blocks where the blocked 
address visited the wiki between roughly 08:05 and 09:25 UTC 11 January, 

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