Page MenuHomePhabricator

<ref>...</ref> in template
Closed, DuplicatePublic

Description

Author: orenbochman

Description:
within templates contents of ref tags is not expanded e.g. <ref>{{{cite}}}<ref>
will generate a reference is the literal "{{{cite}}}"

This has led to fragile templates based on "tag" templates and makes automation of references impractical.


Version: unspecified
Severity: normal

Details

Reference
bz29775

Event Timeline

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

{{#tag:ref|bla {{{cite}}} bla}} ought to expand parameters in the way you expect; give it a try and see if that helps.

feels more like bug #2700 to me since bug #2257 is closed.

  • This bug has been marked as a duplicate of bug 2700 ***

orenbochman wrote:

Brion Vibber & Mark A. Hershberger

Thanks for the work around.

However it did take me about 5 hours of tinkering to get the template to working properly. Passing an argument is documented inconsistently. And there is both a parser function #tag and a template tag.

Surely we cannot wiki contributors - who will see their articles deleted or censured by academia (for lack of proper citation) - to become parser function hacking ninjas like ... us?

I understand your wish to reduce the number of pending bugs in Bugzilla. I however am not convinced that this is the same as bug 2700. There are issues related to the tag's attributes and to printing that are complicated to detail at this point.

I therefore humbly request you unmark it as a resolved or as a dupe untill it has actually been fixed by the patch for 2700 (not just on a development machine) without resorting to a 5 hour work around.

Otherwise you are just sweeping the bug under the carpet.

p.s. please advise how to apply the related patch, and if that could have side effects.

(In reply to comment #4)

I therefore humbly request you unmark it as a resolved or as a dupe untill it
has actually been fixed by the patch for 2700 (not just on a development
machine) without resorting to a 5 hour work around.

Otherwise you are just sweeping the bug under the carpet.

If it is marked as a dupe and the fix to 2700 doesn't fix the bug, then please reopen the bug. Marking bugs as duplicates is not sweeping them under the carpet ... it helps us keep track of how important a bug is.

p.s. please advise how to apply the related patch, and if that could have side
effects.

The patch supplied on #2700 is not valid.