(In reply to comment #0)

The <Centralauth-error-locked> message sucks and needs improvement - it
currently reads:

You cannot edit because your account is locked.

This compares poorly to <Globalblocking-blocked> in terms of giving users
somewhere to go:

Your IP address $5 has been blocked on all wikis by $1 ($2). The reason

given
was "$3". The block $4.

(This is being changed right now anyway.)

Does the extension even give an error when logging in? I think it's just the incorrect passwd message.

James: should this bug continue to be assigned to you?

(In reply to comment #2)

James: should this bug continue to be assigned to you?

Bump.

And did https://gerrit.wikimedia.org/r/98568 fix this bug? Can someone check?

(In reply to MZMcBride from comment #3)

(In reply to comment #2)

James: should this bug continue to be assigned to you?

Bump.

And did https://gerrit.wikimedia.org/r/98568 fix this bug? Can someone
check?

This bug is about Centralauth-error-locked, not Centralauth-login-error-locked. Also, that did not include any detailed info like the reason for being locked.

(In reply to James Forrester from comment #0)
Are you still working on this?

(In reply to PiRSquared17 from comment #4)

This bug is about Centralauth-error-locked, not
Centralauth-login-error-locked. Also, that did not include any detailed
info like the reason for being locked.

Can you submit a patch please?

(In reply to Nemo from comment #6)

(In reply to PiRSquared17 from comment #4)

This bug is about Centralauth-error-locked, not
Centralauth-login-error-locked. Also, that did not include any detailed
info like the reason for being locked.

Can you submit a patch please?

This is nontrivial, like bug 61548. The lock reasons are not stored in a central location currently. Using the current scheme, we would need to query every wiki (since locks can be from any wiki). Perhaps it would be better to create a central location for the globalauth logs or at least the current locks (maybe in globaluser table?).

James, are you still interested in this?

There is a bug about restricting changes of global groups rights and membership to the central wiki; there is probably also one for locks. If that's a requirement for this bug, let's add it to blockers and get all of them done at once.

A temporary fix would be to only look on the "central wiki", and just give the current message if it's not found there.

(In reply to Nemo from comment #8)

There is a bug about restricting changes of global groups rights and
membership to the central wiki; there is probably also one for locks. If
that's a requirement for this bug, let's add it to blockers and get all of
them done at once.

Ticket link?

Not a matter of tone but of availability of correct details to the local wiki.

Change 413248 had a related patch set uploaded (by Gerrit Patch Uploader; owner: Gerrit Patch Uploader):
[mediawiki/extensions/WikimediaMessages@master] Locally override Centralauth-error-locked

https://gerrit.wikimedia.org/r/413248

Change 413248 abandoned by MarcoAurelio:
[mediawiki/extensions/WikimediaMessages@master] Locally override Centralauth-error-locked

Reason:
No longer required.

https://gerrit.wikimedia.org/r/413248

Change 413248 restored by MarcoAurelio:
[mediawiki/extensions/WikimediaMessages@master] Locally override Centralauth-error-locked

https://gerrit.wikimedia.org/r/413248

Note there are two MediaWiki message.

1. MediaWiki:Centralauth-login-error-locked is displayed when someone tries to login a locked account. The message is overrided in WMF production in T216347: Changing globally locked message across Wikimedia wikis: see https://en.wikipedia.org/wiki/MediaWiki:Centralauth-login-error-locked for the message and you can also reproduce the message by trying to log in using username "test" and arbitrary password.
2. MediaWiki:Centralauth-error-locked if someone tries to do some specific non-login action via a locked account. I am not sure what can be done using an account without login. This message is not overrided in WMF production.

Neither of messages provides a field to display performer or lock reason.

I am confused, locked accounts cannot login, how can they try to edit as that account? The only action that they can try to attempt other than login that I can think of is probably to reset their password (and I am not sure if that is allowed and whether it should be allowed). Is there something else? Perhaps someone can tell more from actually reading the code.