Last modified: 2014-02-13 15:35:36 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 T63315, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61315 - Problem parsing when = character is involved
Problem parsing when = character is involved
Status: VERIFIED INVALID
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-13 15:24 UTC by Toni Hermoso Pulido
Modified: 2014-02-13 15:35 UTC (History)
1 user (show)

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


Attachments

Description Toni Hermoso Pulido 2014-02-13 15:24:41 UTC
Hi,

I found this behaviour when dealing with a Semantic MediaWiki parser function (subobject). I imagine it might affect other extensions as well.

Example:

Template Store:
{{#subobject:Program
|Has Name={{{1}}}
|Has URL={{{2}}}
}}

Page:
{{Store|Firefox|http://download.mozilla.org/?product=firefox-27.0&os=win&lang=ca}}

= seems to break the {{{2}}} parameter processing.

Reference: https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/193
Comment 1 Bartosz Dziewoński 2014-02-13 15:27:50 UTC
That is the expected behavior – this template calls expands to the template 'Store' with two parameters:

  1 = Firefox
  http://download.mozilla.org/?product = firefox-27.0&os=win&lang=ca

While unwanted in this case, this is the expected behavior. You can work around this by explicitly passing the second parameter (note the '2='):

  {{Store|Firefox|2=http://download.mozilla.org/?product=firefox-27.0&os=win&lang=ca}}
Comment 2 Toni Hermoso Pulido 2014-02-13 15:35:36 UTC
Thanks! I see using named parameters could address it as well!

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


Navigation
Links