Page MenuHomePhabricator

Special:CentralAuth has no conflict detection whatsoever
Closed, ResolvedPublic

Description

Author: mike.lifeguard+bugs

Description:
Currently, if you lock/hide/lockandhide-conflict with another steward, you get a blank white page. There should be better error handling here.


Version: unspecified
Severity: normal

Details

Reference
bz18057

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 10:30 PM
bzimport set Reference to bz18057.
bzimport added a subscriber: Unknown Object (MLST).

mike.lifeguard+bugs wrote:

With Andrew's new CA form, one would silently overwrite the previously-set status. That is a big problem.

mike.lifeguard+bugs wrote:

(In reply to comment #1)

With Andrew's new CA form, one would silently overwrite the previously-set
status. That is a big problem.

Apologies if this wasn't clear... The rewritten form makes this a much huger problem than it was previously. Previously you'd be stopped from overwriting someone's changes to global account status - now you silently overwrite them, which is badness through and through.

mike.lifeguard+bugs wrote:

vvv, does your recent work cover this?

Hi. The problem remains as Mike.lifeguard reported in comment 1 and comment 2.

However now with the addittion of a "global oversight" function to the Special:CentralAuth form, the problem has increased since you can override, without knowing it a global oversight of abusive usernames; and trying for fix that may be a bit tedious per bug 23654 (and others).

I'd suggest raising the priority to normal or high. Basically an edit-conflict or a block-conflict like system would solve the problem. Thanks.

Added a patch for simple conflict detection. https://gerrit.wikimedia.org/r/50034

hoo added a comment.Mar 1 2013, 7:17 PM

Fixed: Change merged