Last modified: 2006-08-19 05:20:54 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 6629 - Can't block a user that have been blocked before
Can't block a user that have been blocked before
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-07-11 10:22 UTC by Joakim Larsson
Modified: 2006-08-19 05:20 UTC (History)
0 users

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


Description Joakim Larsson 2006-07-11 10:22:40 UTC
I try to block this user whos block has expired but I get the error message
""" is already blocked".
Comment 1 Titoxd 2006-07-14 23:47:04 UTC
This is due to the new changes in the block software.

As this is a bit annoying when blocking vandals, could we get a confirmation
screen instead of an error message, saying:

*"" was already blocked for <TIME> on <TIMESTAMP>. Are you sure you
want to override the block?

Additionally, it could be helpful if we got a snippet of the block log, like the
protection log is shown on ?action=protect and the move log is shown on
?action=move. The log would only show when there is an "already blocked" prompt
thrown, with the target being the intended blockee. Is that a good idea, or am I
just nuts?
Comment 2 Deon 2006-07-15 04:11:58 UTC
Perhaps try unblock then reblock?

Comment 3 Brion Vibber 2006-08-19 05:20:54 UTC
Said to have been fixed in r15482.

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