Page MenuHomePhabricator

Renaming of namespace-2 on MediaWiki for Esperanto and adding namespace redirect to ns:2
Closed, ResolvedPublic

Description

Author: michael.moroni

Description:
[[rev:70350|As in Wikipedia]], Esperanto Wikimedia projects need to change namespace 2 (User:) to a more generic "Uzanto:" instead of the specific "Vikipediisto:" (Wikipedian): This problem influences also non-Wikipedia
project, using MediaWiki: for example, in ScoutWiki (http://eo.scoutwiki.org),
namespace 2 is named "Vikipediisto", that's not correct. So, we'd like to change the namespace as following:

  • "Vikifontaristo" in Wikisource should redirect to "Uzanto";
  • "Vikicitaristo" in Wikiquote should redirect to "Uzanto" (there is only "Vikipediisto" and not "Uzanto" nor "Vikicitaristo");
  • "Vikivortaristo" in Wiktionary should redirect to "Uzanto" (there is already "Uzanto", "Vikipediisto" is a namespace redirect and "Vikivortaristo" doesn't exist);
  • "Vikilibristo" in Wikibooks should redirect to "Uzanto" (there is only "Vikipediisto" and not "Uzanto" nor "Vikilibristo");
  • "Vikiversitatisto" in Wikiversity should redirect to "Uzanto";
  • "Vikinovaĵisto" in Wikinews should redirect to "Uzanto";
  • Non-Wikimedia project should have "Vikipediisto" as redirect to "Uzanto" (b/c);

We don't have neither Wikisource nor Wikiversity nor Wikinews, yet
(source is going to be opened)


Version: unspecified
Severity: enhancement

Details

Reference
bz24637

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 10:59 PM
bzimport set Reference to bz24637.
bzimport added a subscriber: Unknown Object (MLST).

The Wikimedia Foundation has no control over ScoutWiki. They will receive this update automatically when they upgrade to the (unreleased) 1.17 version of MediaWiki or patch their install with r70350.

We can deploy this to Wikipedia though, I'll get right on that.

michael.moroni wrote:

(In reply to comment #1)

The Wikimedia Foundation has no control over ScoutWiki. They will receive this
update automatically when they upgrade to the (unreleased) 1.17 version of
MediaWiki or patch their install with r70350.

Logically, it was only an example in order to make the problem more understandable

(In reply to comment #1)

We can deploy this to Wikipedia though, I'll get right on that.

WikiMedia! The problem in Wikipedia has been fixed in r70350. Now the problem is related to the other Wikimedia project :)

  • Michael

(In reply to comment #2)

(In reply to comment #1)

We can deploy this to Wikipedia though, I'll get right on that.

WikiMedia! The problem in Wikipedia has been fixed in r70350. Now the problem
is related to the other Wikimedia project :)

  • Michael

No, the problem on Wikipedia has not been fixed in r70350, it needs to actually get rolled out. r70350 is a generic fix that will apply to all WMF wikis once deployed and all 3rd-party wikis once they upgrade to a version that includes it. It's not Wikipedia-specific in any way.

r70350 deployed. Trying to clean up unreachable pages on eowiki (other eo wikis were clean) yielded the following:

catrope@fenari:/home/wikipedia/common/wmf-deployment$ php maintenance/namespaceDupes.php --wiki=eowiki --fix --suffix=/BROKEN
... 323777 (0,"Uzanto:Hellsepp") -> (2,"Hellsepp") [[Uzanto:Hellsepp]]
... * cannot resolve automatically; page exists with ID 323847 *
... * old title Hellsepp
...
* new title Hellsepp/BROKEN
... * using suffixed form [[Uzanto:Hellsepp/BROKEN]] *
... resolving on page... ok.
... 328735 (0,"Uzanto:SchnitteUK") -> (2,"SchnitteUK") [[Uzanto:SchnitteUK]]
... * cannot resolve automatically; page exists with ID 328738 *
... * old title SchnitteUK
...
* new title SchnitteUK/BROKEN
... * using suffixed form [[Uzanto:SchnitteUK/BROKEN]] *
... resolving on page... ok.
... 107231 (0,"Uzanto:Wulfgang") -> (2,"Wulfgang") [[Uzanto:Wulfgang]]
... * cannot resolve automatically; page exists with ID 107227 *
... * old title Wulfgang
...
* new title Wulfgang/BROKEN
... * using suffixed form [[Uzanto:Wulfgang/BROKEN]] *
... resolving on page... ok.

This should be cleaned up by local sysops.

michael.moroni wrote:

Thank you!