Page MenuHomePhabricator

CentralAuth: global suppression with this extension should use autoblock
Closed, ResolvedPublic


Dear all,

The CentralAuth extension has been recently updated so that we stewards can globally lockhide an account + locally suppress usernames by using this extension; which locally blocks the username with suppression enabled. That is good but it could be better if it could use autoblock when blocking the username in question (with account creation blocked, email blocked, autoblock enabled, wpHideUser enabled and talk page editing blocked).

Sometimes vandals creates lots of libelous accounts in one wiki until you can checkuser it and block its IP address/range to stop the vandalism spree; and this is happening often disgracefully.

Until bug 17929 gets fixed, this will be a very good fix.

Many thanks in advance for your help and time.

Version: unspecified
Severity: major



Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:59 PM
bzimport set Reference to bz23114.

Fixed in r64982, herr steward.

mike.lifeguard+bugs wrote:

(In reply to comment #1)

Fixed in r64982, herr steward.

Thank you!

(In reply to comment #1)

Fixed in r64982, herr steward.

Platonides, it seems it does not work properly. Right now I've been experiencing problems with a vandal. Perhaps we shoud set:

'ipb_auto' => true,


Thank you.

vvv added a comment.Apr 17 2010, 5:43 PM

(In reply to comment #3)

'ipb_auto' => true,

No, it's for denoting actual autoblocks.

Should be fixed on r65184.