#103512div in ckeditor
Description
As far as I understand it, div-Tags are allowed by default (https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/8.0/Breaking-72837-RTETransformationsAllowDivSectionsByDefaultAndRemoveFont-specificParsing.html#breaking-72837-rte-transformations-allow-div-sections-by-default-and-remove-font-specific-parsing).
My styles.content.allowTags are the default – also containing div
My processing.yaml contains
processing:
mode: default
# Tags that are allowed in the content in general
allowTags:
...
div
and default transformation-settings.
Divs are also allowed in ckeditor by using htmlSupport – { name: ‘div’, attributes: true, classes: true, styles: true }
The div shows up in ckeditor until I press the save-button. After this, the div is stored in the database but replaced by p in ckeditor and rendered as p in FE.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 1
-
Benni Mack commented and changed status
NewClosed 06/21/24, 08:18
This code is not replaced in RTE. This works as expected when using:
Please check your database contents (= what is in the DB table row).
In addition, you should check your “lib.parseFunc_RTE” configuration in Frontend output. There is a option called “remapTag.DIV = P” – this line needs to be unset.
Just use this in your TypoScript:
lib.parseFunc_RTE.nonTypoTagStdWrap.encapsLines.remapTag.DIV >