Unclosed transclusion eats next section in rendering, but not in section editing
Closed, ResolvedPublic


Author: zigger

has an unclosed transclusion in section 14, breaking rendering and
section-editing (from bug 2128 #c5).

Test case:

sec 1


sec 2


sec 3


The test page is rendered without most of section 2, including TOC (if there are
more sections) and section-numbering of edit-links. Editing section 3 then
brings up section 2.

Version: 1.4.x
Severity: normal
URL: http://eo.wikipedia.org/w/index.php?title=Vikipedio:Trukoj/Plurnivela_uzado_de_%C5%9Dablonoj&oldid=155874

bzimport added projects: MediaWiki-Parser, Parser.Via ConduitNov 21 2014, 8:34 PM
bzimport added a subscriber: Unknown Object (MLST).
bzimport set Reference to bz2375.
bzimport created this task.Via LegacyJun 10 2005, 6:57 PM
bzimport added a comment.Via ConduitJun 10 2005, 7:20 PM

avarab wrote:

This is due to the way MediaWiki garbage collects invalid syntax, it should
probably just output a literal


sec 2


Instead of removing it completely from the output.

bzimport added a comment.Via ConduitJun 10 2005, 11:07 PM

gangleri wrote:

Thanks Zigger for debugging the page!

The error described in bug 2128 #c5 refers to &oldid=155874 of
[[eo:Vikipedio:Trukoj/Plurnivela uzado de ŝablonoj]] .
Do not hesitate to revert to this version if you want to experience the
behaviour reported earlier.

The testcase from comment 0 is available at

Regards Reinhardt [[user:gangleri]]

bzimport added a comment.Via ConduitJun 11 2005, 12:09 AM

gangleri wrote:


It might be possible that this behavior could be detected if
"bug 662: Templates inside template parameters"
would be implemented.

The parser should see that the number of opening "{{" is not identical with the
number of "}}".

Anyhow it should be defined what should happen in such cases.

Please compare with
"''bug 885: silent insertion of code by the parser''"

Regards Reinhardt [[user:gangleri]]

bzimport added a comment.Via ConduitJun 22 2005, 6:44 PM

zigger wrote:

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

Add Comment