Last modified: 2012-11-13 20:38:49 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 T21168, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19168 - <includeonly> is broken inside <ref> tags
<includeonly> is broken inside <ref> tags
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Cite (Other open bugs)
unspecified
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 20122 37900 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-12 00:28 UTC by Hesperian
Modified: 2012-11-13 20:38 UTC (History)
5 users (show)

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


Attachments

Description Hesperian 2009-06-12 00:28:45 UTC
<includeonly> does not work within <ref> tags.

Create a page with content
 <ref>A<includeonly>B</includeonly></ref><references/>
Then transclude it into another page. One would expect the transcluded page to contain the "B", but it does not.

I'm ranking this normal rather than minor because the problem is blocking effective footnote overflow handling at the English Wikisource.
Comment 1 Alex Z. 2009-07-14 22:17:50 UTC
Likely the same issue as bug 2257. 
Comment 2 Chad H. 2009-08-09 01:32:41 UTC
*** Bug 20122 has been marked as a duplicate of this bug. ***
Comment 3 P.Copp 2009-11-26 03:29:34 UTC
The cite extension should pass the current frame back to recursiveTagParse to make <ref> work correctly in templates.

Until this is fixed, you could always use  the {{#tag}}-parser function. Try: 

{{#tag:ref|A<includeonly>B</includeonly>}} <references />
Comment 4 Amir E. Aharoni 2012-07-27 15:56:28 UTC
*** Bug 37900 has been marked as a duplicate of this bug. ***

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


Navigation
Links