Page MenuHomePhabricator

Broken interwikis in translation notifications for Wikimania wiki
Closed, ResolvedPublicBUG REPORT

Description

If you receive a translation notification for Wikimania wiki on a different wiki, the interwiki link is broken. See https://de.wikipedia.org/w/index.php?title=Benutzer_Diskussion:Ameisenigel&oldid=230051904#%C3%9Cbersetzungsbenachrichtigung:_2023:Scholarship_Questions as an example. The translation notification is using the interwiki prefix "wm", but this prefix is not defined in the interwiki table. Only "wmania" and "wikimania" are valid prefixes for the Wikimania wiki.

Event Timeline

The msg is MediaWiki:Translationnotifications-talkpage-body.

This might come from the line 'wikimaniawiki' => [ 'wm' ], in wgLocalInterwikis in https://noc.wikimedia.org/conf/InitialiseSettings.php.txt (which has not been touched since 2019)? Let me cook up a patch...

Change 886949 had a related patch set uploaded (by Aklapper; author: Aklapper):

[operations/mediawiki-config@master] Fix interwiki prefix for generic wikimaniawiki

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

Change 886949 merged by jenkins-bot:

[operations/mediawiki-config@master] Fix interwiki prefix for generic wikimaniawiki

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

Mentioned in SAL (#wikimedia-operations) [2023-02-23T00:39:03Z] <zabe@deploy1002> Started scap: Backport for [[gerrit:886949|Fix interwiki prefix for generic wikimaniawiki (T327575)]]

Mentioned in SAL (#wikimedia-operations) [2023-02-23T00:40:53Z] <zabe@deploy1002> aklapper and zabe: Backport for [[gerrit:886949|Fix interwiki prefix for generic wikimaniawiki (T327575)]] synced to the testservers: mwdebug2002.codfw.wmnet, mwdebug1002.eqiad.wmnet, mwdebug1001.eqiad.wmnet, mwdebug2001.codfw.wmnet

Mentioned in SAL (#wikimedia-operations) [2023-02-23T00:47:36Z] <zabe@deploy1002> Finished scap: Backport for [[gerrit:886949|Fix interwiki prefix for generic wikimaniawiki (T327575)]] (duration: 08m 33s)

Thanks Zabe for reviewing, merging, deploying!
This problem should be fixed now. If not, please reopen.