Last modified: 2010-05-15 15:56:45 UTC
Possibly this is not a bug but a feature. It appears to be divergating treatment
in a situation where a unique approach might be expected the more logical way.
A workaround exists, so it might be of little concern. If it was not intended the
way it is, it should however be changed before being used a lot.
WiktionaryZ uses ISO 639-2 codes to identify languages, thus the Russian main page
was stored as http://wiktionaryz.org/Development_wiki:Main_Page/rus (not .../ru)
while the wikies main page, no language selected, is
If you access http://wiktionaryz.org/Development_wiki:Main_Page?uselang=ru ,
you get http://wiktionaryz.org/Development_wiki:Main_Page/ru if the page exists,
else you get the general main page http://wiktionaryz.org/Development_wiki:Main_Page .
Making http://wiktionaryz.org/Development_wiki:Main_Page/ru a redirect to
http://wiktionaryz.org/Development_wiki:Main_Page/rus solves the problem.
That is the workaround.
As a better solution was seen though, to create the page
and store "Wikidata M2:Main Page/rus" in it, just as for all other
strings that appear in http://wiktionaryz.org/MediaWiki:Sidebar
the russian translations have to be stored in their respective pages,
such as http://wiktionaryz.org/MediaWiki:Mainpage/ru ,
http://wiktionaryz.org/MediaWiki:Partners/ru , etc.
while the "no language selected" pages are the ones not having /ru
While working with everything else, including the "no language selected"
ones, this does not work for the URL strings of
http://wiktionaryz.org/MediaWiki:Sidebar when a language is selected.
Bug or feature? At least it appears unneccessary complicated from a users view.
The configuration setting $wgForceUIMsgAsContentMsg should be used for that –
then you will be able to use MediaWiki:Mainpage/ru. It's disabled by default
because most sites are single-language sites, but WikitonaryZ, which is a
multilingual site, should have this enabled for every page which is exist in
multiple languages. Please ask WiktionaryZ site administrators (not the sysops,
but those who can access the sever, I don't know who can do that) to enable that.