Last modified: 2014-04-21 02:29:14 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 T66165, 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 64165 - Re-blocks aren't working
Re-blocks aren't working
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-04-20 21:48 UTC by Ajraddatz
Modified: 2014-04-21 02:29 UTC (History)
4 users (show)

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

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

Description Ajraddatz 2014-04-20 21:48:47 UTC 
Hi, for the last couple of days, blocks entered with a non-default block time (such as the default time for modifying existing blocks) are not blocking anything. Example of this today on meta.wikimedia when I blocked 87.93.0.0/19 with an expiry time of 21:38, 23 April 2014, and it completely removed the block. I had to re-re-block with an expiry time of 3 days for it to work. See https://meta.wikimedia.org/wiki/Special:Log/block
Comment 1 Ajraddatz 2014-04-20 22:17:46 UTC 
Apologies for the email, re-blocking doesn't seem to be the problem. Will investigate further.
Comment 2 George Barnick (Meiko) 2014-04-20 22:24:54 UTC 
Maybe it's an issue with range blocks instead of having to do with the block time. Does it occur if you were to give a non-range block a non-default block time?
Comment 3 Ajraddatz 2014-04-21 02:29:14 UTC 
It occurred last night with a global block by DerHexer; the time stamp was different than usual and the block didn't work. Now it seems that a user is able to create accounts through a rangeblock, but that might have somehow been my fault, even though the IP he was using was part of that range. Maybe I did it wrong?
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