Last modified: 2013-09-04 10:36:30 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 T31334, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29334 - Giving an array for $wgExtensionCredits['descriptionmsg'] breaks Special:Version
Giving an array for $wgExtensionCredits['descriptionmsg'] breaks Special:Version
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
1.17.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-10 09:26 UTC by s7eph4n
Modified: 2013-09-04 10:36 UTC (History)
2 users (show)

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


Attachments
Patch (1.57 KB, patch)
2011-06-10 09:26 UTC, s7eph4n
Details

Description s7eph4n 2011-06-10 09:26:38 UTC
Created attachment 8634 [details]
Patch

Giving an array for $wgExtensionCredits['descriptionmsg'] (i.e. message key plus parameters) breaks Special:Version (giving an Internal Error). The array is passed to wfEmptyMsg which expects a message key.

MediaWiki	1.17.0rc1 (r89818)

(Works on 1.16, did not check on 1.17+.)
Comment 1 Brion Vibber 2011-06-10 18:05:58 UTC
Why would you supply parameters to a static message? What parameter would be available at LocalSettings.php time that would be suitable?
Comment 2 s7eph4n 2011-06-10 18:48:10 UTC
I do not set this parameter at LocalSettings.php time, but in a hook handler. The parameter is a pagename that can be set through a variable in LocalSettings to configure the extension. Setting the variable is done after the require_once for the extension.

(The author of Special:Version obviously also thought, that giving a parameterized message should be possible. He explicitly tests if the message is an array or a string and processes it accordingly.)
Comment 3 Bawolff (Brian Wolff) 2011-06-10 20:40:06 UTC
This was fixed back in r78996 (1.18) by Nikerabbit.

I agree that it seems weird to have a parameter for that, but all our docs say that you can.

I have no idea if this is the type of thing we'd want to backport to 1.17 (Since its a regression) or if its too late for that.
Comment 4 Mark A. Hershberger 2011-06-15 01:19:58 UTC
probably too late for 1.17.0 ... maybe we should make a list of patches for 1.17.1, though.
Comment 5 Bawolff (Brian Wolff) 2011-06-20 20:58:21 UTC
I'm removing the keyword need-review, since the issue is already fixed in trunk, so the patch doesn't really need to be reviewed (hope that's right).
Comment 6 Bawolff (Brian Wolff) 2011-09-08 14:18:26 UTC
I'm going to close this fixed (since it was fixed in 1.18). There's really not much to do here since 1.17 is already long released.

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


Navigation
Links