Last modified: 2008-03-16 18:14:38 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 T9400, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 7400 - Substing bypasses <nowiki>
Substing bypasses <nowiki>
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
: parser
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-24 17:18 UTC by Platonides
Modified: 2008-03-16 18:14 UTC (History)
1 user (show)

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


Attachments
Bug 7400 (697 bytes, patch)
2007-04-15 20:51 UTC, Platonides
Details

Description Platonides 2006-09-24 17:18:29 UTC
A given page with <nowiki>{{subst:PageA}}</nowiki>, when substed on PageB
returns the wikicode of PageA.

You can also see it if you call on a page "Please
<nowiki>{{subst:Template}}</nowiki>" and then {{subst:Template}} on another
page, as it becames <nowiki>[[Template:Template]]<!-- WARNING: template loop
detected --></nowiki>


You can use <nowiki>{{subst:</nowiki>PageA<nowiki>}}</nowiki> or
<nowiki>{{</nowiki>subst:PageA<nowiki>}} as workaround.


Bug or feature?
Comment 1 fuhghettaboutit@yahoo.com (Account disabled) 2007-04-15 15:31:38 UTC
This bug is continuing to cause problems. After I asked as 
the Wikipedia help desk why when I substitituted 
[[User:Fuhghettaboutit/Toolbox]] the nowiki tags were not 
working, I was referred here.--~~~~
Comment 2 Platonides 2007-04-15 20:51:52 UTC
Created attachment 3449 [details]
Bug 7400

This patch fixes this bug. Now, someone familiar enough with the Parser should
check nothing gets broken.

See you at the madhouse.
Comment 3 Nicolas Dumazet 2008-03-16 18:14:38 UTC
Has been fixed with the new parser, apparently.

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


Navigation
Links