Last modified: 2014-02-12 23:55:07 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 T60356, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 58356 - array( 'parse' ) causes the message to be always in English
array( 'parse' ) causes the message to be always in English
Status: RESOLVED WORKSFORME
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Normal normal
: ---
Assigned To: Nobody - You can work on this!
: easy
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-11 23:27 UTC by Juliusz Gonera
Modified: 2014-02-12 23:55 UTC (History)
10 users (show)

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


Attachments

Description Juliusz Gonera 2013-12-11 23:27:00 UTC
To reproduce:

Open your wiki with ?uselang=ja as a query string, open mobile editor. The heading should be in Japanese. It's not.
Comment 1 Bingle 2013-12-11 23:35:29 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1502
Comment 2 Juliusz Gonera 2013-12-12 00:50:40 UTC
This happens only with ?uselang=xx not when setting the language in LocalSetting.php so it's not as critical as I thought.
Comment 3 Jon 2013-12-12 23:32:17 UTC
The offending line is in MFResourceLoaderModule.php

wfMessage( $key )->parse();

I suspect wfMessage in this context is not familiar with the current language.
Comment 4 Jared Flores 2013-12-24 10:58:16 UTC
Just a quick question: What are the "headings" in the mobile editor?
Comment 5 Max Semenik 2013-12-24 15:52:29 UTC
Can't repro - maybe the particular message wasn't localized at the time?
Comment 6 Jon 2013-12-24 17:04:34 UTC
Yeh I can't reproduce either...

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


Navigation
Links