Last modified: 2010-05-15 15:29:12 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 T2553, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 553 - link with two variables in a piped link
link with two variables in a piped link
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
1.3.x
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://meta.wikimedia.org/wiki/Templa...
: parser
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2004-09-22 02:33 UTC by Suisui
Modified: 2010-05-15 15:29 UTC (History)
0 users

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


Attachments

Description Suisui 2004-09-22 02:33:55 UTC
Please see URL's source, and how display it is.
I just want use like this way.
http://meta.wikimedia.org/wiki/User:Suisui/sandbox
Yes it works.
But on the list of templates, it shows stronge one.

When I write as
[[wikisource:{{PAGENAME}}|{{{1}}}]]
then it looks good. but
[[wikisource:{{{1}}}|{{{2}}}]]
does not works good.
Comment 1 Wil Mahan 2004-10-01 20:49:44 UTC
If I understand correctly, you're referring to the fact that the template
page [[Template:Wikisource]] looks strange, even though it works correctly
when you include the template in another page.

There is indeed a problem here. A simpler test case is:

{|
|[[{{{1}}}|{{{2}}}]]
|}

When displaying the page, the link is not parsed because it contains the
characters '{' and '}'. However, the table parsing code thinks that the '|'
in the link indicates table cell parameters. I'll try to find a fix
for this in the near future.
Comment 2 Wil Mahan 2004-10-01 21:23:05 UTC
Should be fixed in HEAD (Parser.php revision 1.314).
Comment 3 Daniel Kinzler 2004-11-09 21:22:31 UTC
hm, why is this bug now marked "fixed-in-cvs"? The parser-bug was fixed, but
this didn't give us defaults for parameters / optional parameters, right? Or
this this already implemented too? That would be cool!
Comment 4 Brion Vibber 2004-12-11 23:28:56 UTC
Not sure I understand which issue this bug is about.
Comment 5 Brion Vibber 2005-01-30 05:06:21 UTC
Resolving as fixed as it's described above as fixed in what is now REL1_4.

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


Navigation
Links