Page MenuHomePhabricator

Globalblocking-ipblocked-range doesn't show an actual link to the username, but wiki syntax with square brackets
Closed, DuplicatePublic

Description

The message Globalblocking-ipblocked-range is supposed to show a link to the username. It is sent as a parameter, and uses square brackets. When it's actually shown, it is not parsed, and the square brackets are shown.

I saw this on a phone, so maybe it's a MobileFrontend-specific issue, and maybe it's broken on all platforms.

Event Timeline

@Amire80 - do you have reproduction steps or somewhere we can replicate this?

Globally-block a range, and try to edit. You'll see this message.

@Amire80 not all of us have permission or are familiar with the protocols for doing such a thing. Could you provide some clear replication steps e.g. URLS to special pages with instructions what to put in boxes and what to expect? This would help us investigate this and prioritise this.

Can you try it from the SF office, by any chance? I think it's globally blocked (to remind staff to log in :)

Are you talking about the toast message? I'm not seeing an issue:

Screen Shot 2017-04-10 at 1.14.38 PM.png (594×738 px, 147 KB)

Is this a duplicate of T155835 ?

Amire80 renamed this task from Globalblocking-ipblocked-range does show an actual link to the username, but wiki syntax with square brackets to Globalblocking-ipblocked-range doesn't show an actual link to the username, but wiki syntax with square brackets.Apr 11 2017, 7:34 AM

Ow, wrote a reply and didn't press the Submit button!

No, not this toast. This is a different message:
https://translatewiki.net/wiki/MediaWiki:Globalblocking-ipblocked-range/en

Not sure where is this one shown. I'll try to find a way to reproduce this.

The general issue here is that the mobile web toast only accepts plain text not HTML. The toast doesn't parse. I've generalised T155835 to cover this issue as well. Can you add a screenshot to T155835? Let's track this issue there.

Mmm, I'm pretty sure that it was not a toast at all.

Okay.. screenshot would definitely help here :)
but sounds like it's an issue in GlobalBlocking extension not MobileFrontend since toasts are the only way we provide notifications.