Last modified: 2012-04-12 13:55:25 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 T30641, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 28641 - wfEmptyMsg doc
wfEmptyMsg doc
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Documentation (Other open bugs)
1.16.x
All All
: Lowest trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-04-21 13:08 UTC by Liangent
Modified: 2012-04-12 13:55 UTC (History)
3 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Liangent 2011-04-21 13:08:16 UTC 
The doc comment above it doesn't conform to how it works.
Comment 1 Mark A. Hershberger 2011-04-21 22:05:13 UTC 
It does say it returns boolean (at least in trunk).  What did you want?
Comment 2 Liangent 2011-04-22 04:44:00 UTC 
"by looking at wfMsg() output" doesn't match its current implementation (it was working in that way).
Comment 3 Niklas Laxström 2011-04-22 10:06:28 UTC 
wfMsgEmpty is going to be deprecated in favour wfMessage()->exists().
Comment 4 Chad H. 2011-05-05 05:26:58 UTC 
I imagine it'll remain for quite some time...the wfMsg* functions have been around for ages and we can't get rid of them all at once. Fixed the docs in r87481.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links