Last modified: 2010-05-15 15:37:54 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 T5206, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 3206 - Problem with how software deals with multiple concurrent blocks.
Problem with how software deals with multiple concurrent blocks.
Status: RESOLVED DUPLICATE of bug 2492
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Normal normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 4618
  Show dependency treegraph
Reported: 2005-08-20 04:19 UTC by Matthew Flaschen
Modified: 2010-05-15 15:37 UTC (History)
1 user (show)

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


Description Matthew Flaschen 2005-08-20 04:19:25 UTC
When there is a short and long block on the same user concurrently, the user
becomes unblocked when the shorter time period expires, when it should be the
longer time period(or possibly the sum).  See

, which is below:

"Blocks washing off in the rain?

I have a feeling that users are becoming unblocked without any admin action. For
example, I know that an account of the Willy on Wheels vandal were blocked
indefinitely several months ago, yet it was able to vandalize recently.

Also, on en-Wiktionary, the vandal "ConneI MacKenzie" (impersonating user Connel
MacKenzie) was blocked indefinitely, yet he disappeared from the IP block list,
and no record of him being unblocked could be found in the block log. --Ixfd64
22:23, 2005 August 16 (UTC)

When an account or IP is blocked more than once with differing lengths, it
becomes unblocked when the shortest one expires. ConneI MacKenzie was blocked
for one week and indefinitely; therefore his block ran out after one week.
—Cryptic (talk) 23:19, 16 August 2005 (UTC)

        That sounds backwards. Shouldn't it be when the longest one expires? —
Nowhither 23:57, 16 August 2005 (UTC)

            That's what I thought too. --Ixfd64 00:03, 2005 August 17 (UTC)

            You'd think, but the software probably checks the database every x
amount of time for expired blocks, and then unblocks those cases, causing this
behavior. — Ilγαηερ (Tαlκ) 00:06, 17 August 2005 (UTC)

                I should probably fix Wikipedia:Blocking policy then. --Ixfd64
01:15, 2005 August 18 (UTC)

                    No. This is a bug. I'm posting it to Zilla. Superm401 | Talk
04:13, August 20, 2005 (UTC)

Comment 1 Matthew Flaschen 2006-01-14 19:04:13 UTC
I've since learned that this is the known state of affairs.  Please remove the bug.
Comment 2 Rob Church 2006-01-15 05:48:20 UTC
We can't remove the bug. However, I'm working on improvements to the blocking
page, e.g. bug 1496, and the cause of this will be reduced as a result, since
users will not be double or triple blocked by admins who don't know that a block
exists, and block with varying lengths of time.
Comment 3 Matthew Flaschen 2006-01-15 06:23:21 UTC
Excuse me.  I meant close it.
Comment 4 Rob Church 2006-01-16 02:08:29 UTC

*** This bug has been marked as a duplicate of 2492 ***

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