Page MenuHomePhabricator

set $wgInterwikiMagic to true multilingual Wikisource
Closed, ResolvedPublic

Description

Author: brendan

Description:
Overview: Interlanguage links on the multilingual Wikisource don't produce sidebar links, instead producing normal inline links as if they had a forcing colon prefixed.

Steps to reproduce: View [[oldwikisource:User:Prosody]].

Actual results: inline link to [[s:en:User:Prosody]] with body "en:User:Prosody."

Expected results: sidebar section "In other languages" with link to
[[s:en:User:Prosody]] with body "English."


Version: unspecified
Severity: normal
URL: http://wikisource.org/wiki/Wikisource:Scriptorium#Seeking_consensus_for_working_interlanguage_links

Details

Reference
bz29534

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 21 2014, 11:30 PM
bzimport set Reference to bz29534.
bzimport added a subscriber: Unknown Object (MLST).

This appears to be an intentionally set configuration option ($wgInterwikiMagic). In order to change it you need to get community consensus at oldwikisource.

I'm resolving this bug as later (is that right?). Please re-open if you have agreement at Wikisource.

Cheers.

brendan wrote:

I guess we've got a quorum, all in favor, at oldwikisource:Wikisource:Scriptorium#Seeking_consensus_for_working_interlanguage_links.

For reference the url is http://wikisource.org/wiki/Wikisource:Scriptorium#Seeking_consensus_for_working_interlanguage_links (perma-link http://wikisource.org/w/index.php?title=Wikisource:Scriptorium&oldid=313449#Seeking_consensus_for_working_interlanguage_links )

There's also talk about changing where the inetlanguage links go, to make them go to wikisource languages (instead of Wikipedia). That should probably be filed as a separate bug.

Doned

<logmsgbot> !log reedy synchronized php-1.17/wmf-config/InitialiseSettings.php 'bug 29534 set to true multilingual Wikisource'
<morebots> Logged the message, Master

bugs wrote:

This is working, but it links to Wikipedia and not Wikisource. I don't think that's the intended behavior.

brendan wrote:

There's a followup about that behavior at bug 29591.