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
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
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.
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.