http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692015-11-27T10:15:08ZTYPO3 ForgeTYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880442015-11-27T10:15:08ZMathias Brodalambrodala@pagemachine.de
<ul></ul><p>Do you happen to pass the menu code through lib.parseFunc(_RTE), e.g. due to <code><f:format.html/></code> instead of <code><f:format.raw/></code> in your template?</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880452015-11-27T10:29:37ZRiccardo De Contardierredeco@gmail.com
<ul></ul><p>duplicate, I guess <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Unwanted p tag between UL and LI (Closed)" href="http://forge.typo3.org/issues/65234">#65234</a></p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880482015-11-27T10:35:53ZAndreas Steigertypo3@andreassteiger.de
<ul></ul><p>Mathias Brodala wrote:</p>
<blockquote>
<p>Do you happen to pass the menu code through lib.parseFunc(_RTE), e.g. due to <code><f:format.html/></code> instead of <code><f:format.raw/></code> in your template?</p>
</blockquote>
<p>Indeed! the empty tags are not be rendered in <f:format:raw> - but why?</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880562015-11-27T10:51:02ZMathias Brodalambrodala@pagemachine.de
<ul></ul><p>Because <code><f:format.raw/></code> simply disables the HTML escaping applied by default in Fluid. OTOH <code><f:format.html/></code> by default passes its content through <code>lib.parseFunc</code> which by default puts paragraphs around empty lines by default since they are stored like this when editing via RTE.</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880592015-11-27T10:53:42ZMathias Brodalambrodala@pagemachine.de
<ul></ul><p>Can we assume this is fixed for you?</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880612015-11-27T10:56:48ZRiccardo De Contardierredeco@gmail.com
<ul></ul><p>I don't think that the problem can be considered fixed; But I would close this as duplicate of <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Unwanted p tag between UL and LI (Closed)" href="http://forge.typo3.org/issues/65234">#65234</a></p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880622015-11-27T10:58:19ZMathias Brodalambrodala@pagemachine.de
<ul></ul><p>Well, it is fixed if you use the correct viewhelper depending on the input. For user input possibly created via RTE use <code><f:format.html/></code>, for code generated e.g. by TypoScript use <code><f:format.raw/></code>. That's how it has always been and is not a bug. ;-)</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880772015-11-27T12:29:20ZRiccardo De Contardierredeco@gmail.com
<ul></ul><p>@mathias pardon me if I disagree, but I think that this issue is only about the output of the RTE, and the issue is about a wrong behavior of lib.parseFunc; this IMO, of course.</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=2880832015-11-27T12:49:41ZMathias Brodalambrodala@pagemachine.de
<ul></ul><p>The RTE must not be involved here at all, it's simply that <code><f:format.html/></code> uses its <code>lib.parseFunc_RTE</code>. And <code>lib.parseFunc_RTE</code> behaves correctly since paragraphs are not stored in the database thus must be wrapped on output.</p>
<p>It could be argued whether <code><f:format.html/></code> should use <code>lib.parseFunc</code> by default instead but that would mean a breaking change.</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=3046012016-05-15T18:28:19ZRiccardo De Contardierredeco@gmail.com
<ul></ul><p>Now that I tried to reproduce it using a Typoscript menu I understand what happens:<br />My test (latest 8.2-dev master):</p>
<p>1) create a TS menu:</p>
<pre>
lib.mainmenu=HMENU
lib.mainmenu{
1=TMENU
1.wrap = <ul>|</ul>
1.NO = 1
1.NO.wrapItemAndSub = <li>|</li>
1.expAll =1
2 < .1
3 < .2
4 < .3
}
</pre><br />2) in your Fluid Template, put:
<pre>
<f:format.html>
<f:cObject typoscriptObjectPath="lib.mainmenu"/>
</f:format.html>
</pre>
<p>3) Result: there are some empty<br /><pre>
<p>&nbsp;</p>
<p>&nbsp;</p>
</pre> <br />after the menu. these empty paragraphs are generated indipendently from the presence of the menu object: they would be there even if you write:<br /><pre>
<f:format.html>
</f:format.html>
</pre><br />and disappear if you write <br /><pre>
<f:format.html><f:cObject typoscriptObjectPath="lib.mainmenu"/></f:format.html>
</pre></p>
<p>I think it can be safely closed now.</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=3046022016-05-15T18:40:50ZRiccardo De Contardierredeco@gmail.com
<ul></ul><p>[update] on my previous comment I have not considered the case "fluid styled content".<br />Test with 7.6.6:</p>
<p>1) create a FSC "Text with media" and put in the text a nested list like:</p>
<pre>
<ul><li>Arrivederci<ul><li>ciao</li><li>ciao</li></ul></li><li>ciao</li></ul>
<p>&nbsp;</p>
</pre><br />(so hit enter a couple of time to obtain an empty p after building the list)
<p>2) result on frontend: the empty p is duplicated because the Partial Textmedia.html has:</p>
<pre>
<f:format.html>{data.bodytext}</f:format.html>
</pre> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=3188902016-12-02T10:30:36ZPaul Klimekinfo@paul-klimek.de
<ul></ul><p>Is there any solution or work around?<br />Have the same problem with p-tags on 7.6.10 :(</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=3211642017-01-10T18:51:51Zmartin zarthmartin@zarthwork.de
<ul></ul><p>In 6.2 <code><f:format.html parseFuncTSPath=""></code> did the trick for me.</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=3466422017-10-22T20:50:27ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs Feedback</i></li></ul><p>I performed a test with 8.7.7 and was not able to reproduce this issue</p>
<p>- using a standard Text element (see my comment n°11)<br />- with the setup I described in my comment n°10</p>
<p>Do you think that this can be closed? Or a different test should be done? Thank you!</p>
<p>[EDIT] I think that I was not able to reproduce it because of this <a class="external" href="https://forge.typo3.org/issues/65234#note-27">https://forge.typo3.org/issues/65234#note-27</a> (I used fluid_styled_content)</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=3496122017-10-27T12:49:41ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Category</strong> changed from <i>Content Rendering</i> to <i>Frontend</i></li></ul> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=3601502018-03-09T11:14:38ZAlexander Opitzopitz.alexander@googlemail.com
<ul><li><strong>Status</strong> changed from <i>Needs Feedback</i> to <i>Closed</i></li></ul><p>No feedback within the last 90 days => closing this issue.</p>
<p>If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=4203572020-03-24T18:56:32ZMarkus Mächleradmin@bithost.ch
<ul></ul><p>We faced a very similar issue where between all <p> tags with content there was some empty <p> tag added. E.g.</p>
<p><strong>Text in RTE</strong></p>
<pre>
Lorem
ipsum
</pre>
<p><strong>Text in RTE (HTML view)</strong></p>
<pre>
<p>Lorem</p>
<p>ipsum</p>
</pre>
<p><strong>Frontend rendering</strong></p>
<pre>
<p>Lorem</p>
<p>&npsp;</p>
<p>ipsum</p>
</pre>
<p>The problem was that we set <strong>RTE.default.proc.overruleMode = ts_css</strong> in our TS Config, setting it back to default resolved the issue (<strong>RTE.default.proc.overruleMode = default</strong>). In my opinion the dealing with line breaks in <strong>RteHtmlParser</strong> (e.g. streamlineLineBreaksForProcessing) is extremely error prone and should probably be simplified.</p> TYPO3 Core - Bug #71878: Empty <p>-Tags after Content Renderinghttp://forge.typo3.org/issues/71878?journal_id=4203592020-03-24T18:57:13ZMarkus Mächleradmin@bithost.ch
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-4 priority-default" href="/issues/89429">Bug #89429</a>: Empty p tags added in RTE when changing type "passthrough" to "text" via "columnsOverrides"</i> added</li></ul>