tt_content.bodytext normally contains HTML. According to FSC the currently by luxletter used lib.parseFunc "Creates persistent ParseFunc setup for non-HTML content." while lib.parseFunc_RTE "Creates persistent ParseFunc setup for RTE content (which is mainly HTML) based on the "default" transformation.". To support all features (and manipulations) of RTE content, we should follow TYPO3 default behaviour.
tt_content.bodytext will now be parsed by lib.parseFunc_RTE.
tt_content.bodytext
normally contains HTML. According to FSC the currently by luxletter usedlib.parseFunc
"Creates persistent ParseFunc setup for non-HTML content." whilelib.parseFunc_RTE
"Creates persistent ParseFunc setup for RTE content (which is mainly HTML) based on the "default" transformation.". To support all features (and manipulations) of RTE content, we should follow TYPO3 default behaviour.tt_content.bodytext
will now be parsed bylib.parseFunc_RTE
.See: EXT:fluid_styled_content/Configuration/TypoScript/Helper/ParseFunc.typoscript
Related: https://projekte.in2code.de/issues/