| GMikesell-WMF | |
| Mar 5 2025, 5:23 PM |
| F58614305: Screenshot from 2025-03-05 14-44-58.png | |
| Mar 5 2025, 7:48 PM |
| F58613627: 2025-03-05_09-11-10.png | |
| Mar 5 2025, 5:23 PM |
| F58613625: 2025-03-05_09-10-46.png | |
| Mar 5 2025, 5:23 PM |
Steps to replicate the issue (include links if applicable):
What happens?:
The block information is missing from Special:CentralAuth, making it unclear if a user is blocked.
What should have happened instead?:
Special:CentralAuth should display block details for the user, consistent with how it appears in production.
Other information (browser name/version, screenshots, etc.):
 |  |
@GMikesell-WMF It looks like in the first screenshot, you blocked Betatester but in the second you're looking at Betatesterone
https://test.wikipedia.beta.wmflabs.org/wiki/Special:CentralAuth/Betatester shows correctly that Betatester is blocked on testwiki.
False alarm, perhaps?
Even so, I don't know that we have tested CentralAuth with Multiblocks enabled ($wgEnableMultiBlocks). There may still be some work to do.
Specifically, I suspect CentralAuth just grabs the first block and shows the reason and block parameters for that block. That's fine with multiblocks off, but when they are on, which block do we show? All of them? I was thinking we could similar to what we did for T384916: Update block log snippets for multiblocks and including a message indicating the total number of blocks (that includes a link to Special:BlockList for that user), and show the reason and block parameters for the most recent one.
I did the following tests:
I couldn't reproduce the bug as described. If there is a bug here, please reopen with a more specific reproduction procedure.