Page MenuHomePhabricator

Broken HTML showing up in block log on [[Special:CentralAuth]]: templates are parsed
Closed, ResolvedPublic

Description

I was doing more indepth testing of bug 45412 and figured out that if you block indefinitely, the log entry is rendered normally, but if you set an expiry (like I did at [[Special:CentralAuth/Legosock]]) any links and templates show up as broken HTML, with a link to the users local block log.

If you include a template, like [[Template:blocked proxy]], it renders it, and then shows a lot more broken html.

Ideally both block lengths should have the same behavior, linking to the local block log.


Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=45412

Details

Reference
bz45629

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:39 AM
bzimport set Reference to bz45629.
bzimport added a subscriber: Unknown Object (MLST).

Clarifying: When using a template as a block reason, and blocking an account indefinitely, the template is parsing into the [[Special:CentralAuth]] page for the account.

Desired behaviour is that the template does not parse, and the CentralAuth block reason should simply show the block reason encased in the template markup (e.g., it should "read" as {{schoolblock}}). The content of the template is not relevant in any way to CentralAuth, only to the blocked user.

Examples of problem: https://en.wikipedia.org/wiki/Special:CentralAuth/Amanda_Smalls and https://en.wikipedia.org/w/index.php?title=Special%3ACentralAuth&target=YouthBandsinc

Just for those who are unaware: The 'not parsing' is the norm for how block reasons appear in, for example, the block lost ( https://en.wikipedia.org/w/index.php?title=Special:Log/block&page=User%3AAmanda+Smalls ) including the block reason shown on the contributions page etc (hence why it is the expected way to be shown on centralAuth... and I SWEAR was how it was shown before...)

It looks like the fix for T47412, I7e8109ea, fixes this as well. It's already fixed on group0, and it arrives at group1 and group2 next week.

Jackmcbarn claimed this task.