#72898DataHandler ignores type dependent RTE transformation configuration for new content elements
Description
The DataHandler does not use the correct RTE transformation configuration, if
- the RTE configuration is dependent on the records type value.
- AND it is working on a new content element (uid=“NEW12345…”)
Steps to reproduce in TYPO3 8 and TYPO3 7.6:
- Set the following Page TSConfig
# Allow to create text and textmedia content elements without saving
mod.wizards.newContentElement.wizardItems.common.show = header, text, textmedia
# Allow only p and br tags in the default RTE configuration
RTE.default.proc.entryHTMLparser_db.allowTags = p, br
# extend the list of allowed tags for "text" elements.
RTE.config.tt_content.bodytext.types.text {
proc.entryHTMLparser_db.allowTags := addToList(ul, li)
}
After setting the PageTSConf,
- Create a new “text” element by using the new content element wizard
- Add an unsorted list (ul) to the RTE bodytext field
- Save&Close the element
Expected result: As ul and li are allowed for text elements, they should not be removed or escaped, but written to the database
Real result: The ul and li tags will be escaped. The result is an HTML string visible to the editor.
This does not happen if you save the record, before adding the unsorted list to the bodytext.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.