Last modified: 2006-11-10 23:09:09 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 1496 - Disallow blocking when user is already in block list
Disallow blocking when user is already in block list
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: High enhancement with 5 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 4618
  Show dependency treegraph
 
Reported: 2005-02-08 18:38 UTC by Jeff Bonham
Modified: 2006-11-10 23:09 UTC (History)
0 users

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


Attachments

Description Jeff Bonham 2005-02-08 18:38:51 UTC
Please do not allow a block form to succeed when a user is already blocked.
Comment 1 Daniel Kinzler 2005-05-02 00:58:13 UTC
Disallowing it is not a good idea, because one may need to extend the block
period and/or change the reason for blocking the user for the records. But I
belive showing a message on the confirmation page that informs the admin that
the user is already blocked (and by whome, until when, for what reason) would be
very helpful.

See also the related bug #2044.
Comment 2 p_simoons 2005-08-30 18:06:22 UTC
Showing a warning "this user is already blocked until <time>" would be very useful.
Comment 3 Darkoneko 2005-12-29 00:38:16 UTC
>Disallowing it is not a good idea, because one may need to extend the block
>period and/or change the reason for blocking the user for the records.

if he tries to expend the block period without deleting the other block, the
first block ending will delete all the others.

but well, I agree with the general idea, it's such a bother to have 3 or 4 times
the same name on the ipblocklist
Comment 4 Rob Church 2006-01-14 22:37:16 UTC
I would suggest having the block form do a quick check to see if a block is
effective, and if so, return a quick confirmation - "User Foo blocked this
user/IP on XXX with the reason YYY" - clicking Block again would confirm the block.

If no sizeable objections raise their heads by the time I get round to it, I'll
implement this. Ideas? Feedback? Let's have it.
Comment 5 Tom Preuss 2006-03-11 20:01:09 UTC
(In reply to comment #4)
> I would suggest having the block form do a quick check to see if a block is
> effective, and if so, return a quick confirmation - "User Foo blocked this
> user/IP on XXX with the reason YYY" - clicking Block again would confirm the
block.
> 
> If no sizeable objections raise their heads by the time I get round to it, I'll
> implement this. Ideas? Feedback? Let's have it.

Sounds like a good idea to me.

Comment 6 Rémi Kaupp 2006-04-03 22:42:54 UTC
Yes, sounds very good, it has been discussed on fr.wikipedia admins' blog today 
after a user was blocked 4 times in a row. Full support from me, I don't see any 
drawbacks to this.
Comment 7 Guillaume Paumier 2006-04-04 06:45:41 UTC
+1
Comment 8 Brion Vibber 2006-04-04 06:53:26 UTC
For IPs, how should we handle conflicting autoblocks?
Comment 9 wartdark 2006-04-08 21:42:27 UTC
After many mistakes, I support the idea of a request for confirmation to any
blocking (IPs or recorded users) like Korrigan.
Comment 10 Andrew Garrett 2006-11-10 23:09:09 UTC
This was fixed a while back by Tim Starling in his blocking changes.

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


Navigation
Links