Page MenuHomeMiraheze

Update configuration for MirahezeMagic interwiki wikilinks to apply to log actions, edit summaries, and page previews
Open, NormalPublic

Description

Issue: I was discussing this with @Reception123 a few weeks back when I wondered whether we should have a MirahezeMagic project on Phabricator, and he suggested I use either Configuration or MediaWiki for now. Anyway, the MirahezeMagic interwiki wikilinks that take the form of [[mh:subdomain:pageName|optional piped link]] only display on pages, not in log actions or edit summaries or when previewing the page. It may be more challenging to update this when previewing the page, so if that can't be done, I would be okay with that, but would love to this fixed so we link to specific pages or diffs on other Miraheze wikis in our log actions and edit summaries.

Problem: In log actions, edit summaries, and when previewing the page, the MirahezeMagic interwiki wikilinks appear as redlinks to non-existent pages on that wiki (i.e., Mh:subdomain:pagename|optional piped link).

Reproducable? Yes, on any Miraheze wiki.

What should happen: Instead of formatting the link as a redlink to a non-existent page on the local wiki in log actions, edit summaries, and, ideally, when previewing the page, the MirahezeMagic interwiki wikilinks should be displayed as they would on a page, as interwiki links to the referenced Miraheze customer wiki.

Event Timeline

Dmehus triaged this task as Normal priority.Thu, Sep 24, 21:15
Dmehus created this task.
Dmehus updated the task description. (Show Details)

And why can I never use code blocks on Phabricator tickets anymore? It used to work by using three apostrophes (to left of the 1 key) inline. Now it only seems to work when the code block is in a separate paragraph on its own. This is undesirable behaviour, sub-optimal, and probably should be fixed.

And why can I never use code blocks on Phabricator tickets anymore? It used to work by using three apostrophes (to left of the 1 key) inline. Now it only seems to work when the code block is in a separate paragraph on its own. This is undesirable behaviour, sub-optimal, and probably should be fixed.

`inline code` (a single apostrophe on each side) should work

working example: inline code