https://bugzilla.wikimedia.org/show_bug.cgi?id=20707
Gadget850 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|Low |High Severity|minor |major --- Comment #7 from Gadget850 <[email protected]> 2011-10-06 13:24:31 UTC --- Here is the working sample from above without templates. Placing <ref name=n2> first throws a "Cite error references no text" and a "Cite error references no key". Using #tag:ref more than once in the list throws the errors. **** text<ref name=n1 group=nested_first/> text<ref name=n2 group=nested_first/>. '''Notes''' {{#tag:references| {{#tag:ref|With nested reference<ref>content of nested reference</ref>|name=n1}} <ref name=n2>With no nested reference</ref> |group=nested_first}} '''References''' <references /> **** I consider this the most egregious issue with cite.php. The inability to easily add a reference to an explanatory note using cite.php has caused the creation and retention of multiple templates for this purpose. In use, most of these templates create duplicate ids, thus rendering invalid HTML and bad in-page linking. The simplest fix from the user standpoint would be to allow <ref> tags to nest, while allowing the #tag:ref hack to still work. Note that many uses of #tag:ref have multiple embedded <refs>s. If we have to add new syntax, then we can deal with it. There is no expectation of multiple nesting, i.e. stuffing a #tag:ref inside a #tag:ref. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
