Last modified: 2013-03-05 09:21:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T44290, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42290 - Message definition missing on pages in custom namespaces
Message definition missing on pages in custom namespaces
Status: RESOLVED WORKSFORME
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
REL1_19-branch
PC Windows Server 2008
: Unprioritized normal (vote)
: ---
Assigned To: Niklas Laxström
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-20 12:47 UTC by MWUser
Modified: 2013-03-05 09:21 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments
No Message definition (16.62 KB, image/png)
2012-11-20 12:48 UTC, MWUser
Details

Description MWUser 2012-11-20 12:47:12 UTC
Hi!

I have two custom namespaces in my mediwiki, NS_F01 and NS_F02. But when I am about to translate a page that belongs to one of the custom namespaces the translate message definition is missing in the pop-box. (See attachment)

Doesn´t translate extension support custom namespaces?

 
I have tried to add the namespaces to $wgTranslateMessageNamespaces but that doesnt change anything.

$wgTranslateMessageNamespaces = array(NS_MEDIAWIKI,NS_MAIN,NS_F01,NS_F02);

Thanks in advance, 
Karin
Comment 1 MWUser 2012-11-20 12:48:03 UTC
Created attachment 11392 [details]
No Message definition
Comment 2 Niklas Laxström 2012-11-20 17:14:11 UTC
It looks like message index is outdated. Can you try running the following command:
 php extensions/Translate/scripts/createMessageIndex.php
Comment 3 MWUser 2012-11-20 21:20:06 UTC
Sorry, no change after running script. 

I did some more testing and found wfAddnamespace (wfAddnamespace(100, 'F01')
function and now the message defintions are displayed. Is this the way you must do to use custom namespaces in translate?

//karin
Comment 4 Niklas Laxström 2012-11-20 21:23:45 UTC
Page translation should work perfectly well in custom namespaces without any extra configuration. I have not been able to reproduce this problem.
Comment 5 Siebrand Mazeland 2013-03-05 09:21:41 UTC
Closing this as WFM per comment 4. Please reopen if there is a scenario to reproduce.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links