TypoScript appends '>' when rendering content from tt_content - typo3

Question

I am trying to upgrade TYPO3 from version 4.6 to 4.7. The extension automaketemplate (0.20) is used for the site templates.
I have the following code to retrieve some content from the tt_content table:
lib.darkbar < styles.content.get
lib.darkbar.select.pidInList = {$contentpage.darkbarPID}
For debugging the actual bodytext in the tt_content table is simply the string 'BODYTEXT'. The rendered content in 4.7 is:
<div id="site-darkbar-navigation">
<!-- CONTENT ELEMENT, uid:96/text [begin] -->
>
<!-- Text: [begin] -->
<p class="bodytext">BODYTEXT</p>
<!-- Text: [end] -->
</div>
In 4.6 I did not have the > sign. Where does it come from?

Answer 1

I assume you somewhere have declared an additional > in your configuration. this might come from PHP, typoscript or fluid-/marker-template.
you might search for something like >> in your sources (like <br />>)
Another possibility (especially after a version change [1]): the rendering of some wraps is done 'unbalanced' (= opening and closing are done in the same TEXT or wrap). there might be a wrap as COA something like:
...wrap.cObject = COA
...wrpa.cObject {
10 = TEXT
10.value = <div class="default
20 = TEXT
20.value = variant
20.if.equals.field = layout
20.if.value = 1
30 = TEXT
30.value = ">|</div>
}
(here the opening and closing is done in the same wrap, but the wrap consists of three TEXTs and the opening is done in 10 and clsing in 30)
While in an earlier version all was done in 10, we now have three parts. If you removed the wrap in the early version just with ...10 > it now leaves an broken HTML-Tag.
You might deactivate one part of your configuration after the other until you can localize the error. (Extensions, Templates, Typoscript)
[1] the rendering of contentelements was always topic of changes to reflect state of the art HTML markup. As the rendering was done primary in typoscript and the static template of CSC each version of TYPO3 had compatibility versions of CSC. In your case you might use the static template compatible to the version of the first build so that modifications to the rendering match the rendering.