Page MenuHomePhabricator

<references /> on a page doesn't list <ref> tags from included templates
Closed, ResolvedPublic

Description

Author: michael.frey

Description:
On Wikibooks we use {{:Name}} for making dynanic printable versions.

It works good, but we have a problem with the references.

Example: http://de.wikibooks.org/wiki/Medizinische_Mikrobiologie:_Druckversion

It seems that included refernces don't work.


Version: unspecified
Severity: normal
URL: http://en.wikipedia.org/wiki/Wikipedia:Reference_Bug

Details

Reference
bz8693

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 9:33 PM
bzimport added a project: Cite.
bzimport set Reference to bz8693.
bzimport added a subscriber: Unknown Object (MLST).

paul wrote:

A demonstration of this behavior can be seen on
http://en.wikipedia.org/wiki/Wikipedia:Reference_Bug which uses the template
Test:References. The <ref> and </ref> tags around a reference in a transcluded
page will show as subscripted bracketed numeric links on the rendered page, but
the references and text are not generated in the <references/> section of that
page. Also see the macro it calls,
http://en.wikipedia.org/wiki/Template:Test:Reference for the examples.

paul wrote:

There is a workaround for this. If a parameter passed to the transcluded page
has a <ref> and </ref> on it, that will show up in the calling page. It is only
when <ref> and </ref> are on the transcluded page that it doesn't work.

webmaster wrote:

Not surprisingly, if you transclude a <ref> and also include a <ref> directly, the transcluded tag shows second.

{{TranscludedRef}} <ref>Normally Cited</ref>

Would display as:
[2] [1]

Also, would this bug be dependant on Bug 4529 ?

webmaster wrote:

Sorry, I meant similar to Bug 4529 ...

ayg wrote:

Yeah, in large part it's the same issue: parser hook stuff isn't done in the same pass as curly-brace stuff.

ayg wrote:

*** Bug 10343 has been marked as a duplicate of this bug. ***

webmaster wrote:

Bug 4529 was closed as a duplicate of Bug 2257.

Bug 2257 has a patch which is awaiting review.
That patch might help this bug as well.