Last modified: 2010-05-15 15:38:11 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 4260 - Template nested tag/inclusion problem
Template nested tag/inclusion problem
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-12-12 18:21 UTC by Christian Sieber
Modified: 2010-05-15 15:38 UTC (History)
0 users

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


Description Christian Sieber 2005-12-12 18:21:47 UTC
Having a problem with including one template within another. Relevant code is as


This is part of "Template:Exercise" on my MediaWiki install. A user calls
{{Exercise}} with the given parameters, which are then passed to {{Exercise
Navbox}} as shown (among other places, hence the doubling up. However, MediaWiki
reads the first two }} in '{{{course}}}' not as a parameter call but as a
closing of the original '{{Exercise Navbox' code. THis results in '{{{course'
being passed to the course variable in the {{Exercise Navbox}} call and the
rest, '}|chapter={{{chapter}}}|section={{{section}}}|foo=bar}}' gets displayed
as simple text.

Can this be fixed?
Comment 1 Christian Sieber 2005-12-12 18:25:25 UTC
Never mind, works when calling the template tag, just not in the display of the
actual template page.
Comment 2 Zigger 2005-12-13 05:31:18 UTC
(re-opened to resolve as INVALID, i.e. not a bug & behaved as designed)

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