TYPO3 Core

This is no solution as then links inside the <li> tags are no more possible.

This seems to work:

lib.parseFunc_RTE.externalBlocks := addToList(li)
lib.parseFunc_RTE.externalBlocks{
        li.stripNL=1
        li.stdWrap.parseFunc = < lib.parseFunc
}

Its true that

lib.parseFunc_RTE.externalBlocks.ul.callRecursive >

lib.parseFunc_RTE.externalBlocks := addToList(li)
lib.parseFunc_RTE.externalBlocks{
        li.stripNL=1
        li.stdWrap.parseFunc = < lib.parseFunc
}

also doesnt work. I get the same result:

<ul>
<p>&nbsp;</p>
<li><a href="/">Prozessoptimierung</a></li>
<p>&nbsp;</p>
<li>Ressourcenauslastung</li>
<p>&nbsp;</p>
<li>Qualitätssteigerung</li>
<p>&nbsp;</p>
<li>Effizienz</li>
<p>&nbsp;</p>
<li>Imagestärkung</li>
<p>&nbsp;</p>
</ul>

Could you try this?
lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.encapsTagList = p,pre,h1,h2,h3,h4,h5,h6,hr,dt,li

I was really wondering because in an other TYPO3 installation (also 6.2.10) which I updated already last year, I found this line which is completely different.Could it perhaps be that the update manager in the install tool didn't terminate properly in V. 6.2.10?

This

lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.encapsTagList = p,pre,h1,h2,h3,h4,h5,h6,hr,dt,li

works for me. Thank you!

Just happened to fall into this trap as well with 6.2.11, PHP 5.5 and static include "CSS Styled Content TYPO3 v4.5"...

For me, lib.parseFunc_RTE.externalBlocks.ul.callRecursive = 0 does not break (page) links.

The other working solution is adding the lines from comment #3 (adding li to externalBlocks).

Another idea I had was trying to remove li from lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.encapsTagList as TYPO3 4.5 (which we are migrating over from) did not have li in encapsTagList. This was sufficient when rendered via TemplaVoila but not outside TV. (Edit: not sure what I tested here, didn't work on retry) However, this doesn't seem to have any effect although that's an obvious difference compared to TYPO3 4.5 (why is it in "CSS Styled Content TYPO3 v4.5", anyway?).

To prevent confusion: Comments #4-#6 are no solution to the original problem; the problem exists with encapsLines defined as in #5/#6 (default).

Edit 2: Another thing about the default code that worries me is that it produced a completely invalid structure on one content element for us: (notice how opening and closing tags are in the wrong order)

<ul><p class="bodytext"><li>Some text: </p><ul><li>link here</li>...</ul><p class="bodytext"></li></p></ul>

I am having the same problem after updating from TYPO3 6.2.6 to TYPO3 6.2.11. So, this is a breaking change.

This bug (?) still occurs in TYPO3 6.2.12.

The problem seems to occur because of a "fix" in #61954.

The following configuration finally worked without breaking something else:

lib.parseFunc_RTE {
    externalBlocks {
        ol >
        ul >
        ol.stripNL = 1
        ol.stdWrap.parseFunc = < lib.parseFunc
        ul.stripNL = 1
        ul.stdWrap.parseFunc = < lib.parseFunc
    }
}

Links inside the nested lists work, too. I did not test click-enlarge images inside an rtehtmlarea.

same problem here with 6.2.13. the above #10 snippet works! thx

The following one-liner works for me as well

# Stop wrapping the following tags with p-tag
lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.encapsTagList = cite, div, p, pre, hr, h1, h2, h3, h4, h5, h6, table, tr, td, th, ul, li

Andreas Becker wrote:

The following one-liner works for me as well
[...]

...but not with nested lists...

Issue still occurs in 6.2.14. The above https://forge.typo3.org/issues/65234#note-10 works for me as well.

This issue should be tagged as a regression.

It is still present on both 6.2.15 and 7.6-dev (latest master), I tried with the standard RTE configuration.

Please have a look at #71878

#71878 doesn't apply for us as the p/ul/li-issue happens outside any Fluid templates for us (regular content elements in TemplaVoila columns).

Stil present in 6.2.26
but Workarround from #10 works for me.

Please be aware, that this is all about nested Lists

It is still present in 7.6.10. The TS-Setup from #10 fixes the problem.

Still present in 6.2 branch. The workaround from #10 worked for me, too. Thank you.

Still present in 6.2.31 and 7.6.18. #10 still works for both versions.

Still present in 8.5.1 but #10 still works.

Patrick Kracht wrote:

Still present in 8.5.1 but #10 still works.

and 8.7.1 only work with #10

The lines

lib.parseFunc_RTE {
    externalBlocks {
        ol {
            stripNL = 1
            stdWrap.parseFunc = < lib.parseFunc
        }
        ul {
            stripNL = 1
            stdWrap.parseFunc = < lib.parseFunc
        }
   }
}

are already present in TYPO3 8.7.1: EXT:fluid_styled_content/Configuration/TypoScript/Helper/ParseFunc.txt

Riccardo De Contardi wrote:

The lines
[...]

are already present in TYPO3 8.7.1: EXT:fluid_styled_content/Configuration/TypoScript/Helper/ParseFunc.txt

ok, but not in EXT:css_styled_content (i know it's deprecated)

The unwanted p-Tag between ul and li doesn't appear any more for TYPO3 8.7.
This applies to both cases: both rendering with fluid-styled-content and rendering with csc-styled-content.

Thanks Patrick for mentioning csc, just stumbled over that misconfiguration. Why is the parseFunc part of csc or fsc? IMHO this hast nothing to do with the way content elements are created / rendered, the editor should behave the same.