Last modified: 2006-02-26 02:28:47 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 5081 - First template argument blank -> non-parsing
First template argument blank -> non-parsing
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-02-25 12:07 UTC by Joel Nothman
Modified: 2006-02-26 02:28 UTC (History)
0 users

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


Description Joel Nothman 2006-02-25 12:07:19 UTC
A recent change to MediaWiki seems to have caused a problem where the first argument to a template was 
left blank. I am failing to duplicate this with other examples (so can't really determine this properly), 
but a template with a commonly-blank first argument is [[Template:Bibleverse]]. Until now, its first 
argument is a bible book number, which most don't have, so {{bibleverse||Psalms|23:2|}} would've been 
valid usage. It used to show an external link labelled "Psalms 23:2". Now, although the template has not 
been changed, it shows as if the code produced by inserting the template has not been processed by 
mediawiki. That is, it shows as [
20Psalms&verse=23:2&src= Psalms 23:2] rather than just a link. See for instance [

Because changing this to {{bibleverse|Psalms||23:2|}} does not change the result of the template, this is 
how the bug has been worked around on affected pages, but this is template-specific.
Comment 1 Brion Vibber 2006-02-26 02:28:47 UTC
This was broken on February 22, apparently due to a misinterpretation of what one 
of our parser tests meant. I've reverted the bogus "fix".

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