Last modified: 2008-07-11 19:29:32 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 7267 - Message cache cannot be accessed via action=raw
Message cache cannot be accessed via action=raw
Product: MediaWiki
Classification: Unclassified
Internationalization (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-09-08 12:29 UTC by Andrew Dunbar
Modified: 2008-07-11 19:29 UTC (History)
2 users (show)

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


Description Andrew Dunbar 2006-09-08 12:29:13 UTC
I'm trying to emulate wfMsg() and wfMsgForContent() with JavaScript

To do this I need to look for a localized message first as a page, and if that
doesn't exist I must then look in the message cache. If there is no localized
message I must then repeat those two steps but look for the plain (nonlocalized)

Now if you look up a page in the MediaWiki: namespace normally or using
action=render and a page doesn't exist but an entry in the message cache does,
you will get the message cache entry wrapped in a div with
class="noarticletext". The page is still empty for purposes of editing etc.

Such is not the case when using action=raw which is the obvious way to access
the strings by JavaScript - even when using the new usemsgcache=yes parameter.

As an alternative to fixing this bug, an addition to query.php which calls wfMsg
/ wfMsgForContent or some other API for JavaScript to get to the interface
strings in the database would be just as good.
Comment 1 Andrew Dunbar 2008-01-20 14:02:24 UTC
See also Bug 12704
Comment 2 Niklas Laxström 2008-07-11 19:29:32 UTC
I assume bug referred in above comment counts "just as good". Resolving to Fixed.

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