Project

General

Profile

Actions

Bug #72898

closed

DataHandler ignores type dependent RTE transformation configuration for new content elements

Added by Hannes Lau almost 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
-
Start date:
2016-01-22
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

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.

Actions #1

Updated by Gerrit Code Review almost 9 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46162

Actions #2

Updated by Hannes Lau almost 9 years ago

I commited a patch that fixes the issue on my TYPO3 7.6 and TYPO3 8 instances.

TYPO3\CMS\Core\DataHandling\DataHander::checkValue_flex_procInData_travDS uses the same array to determine the type value in order to pick the correct RTE configuration.

Actions #3

Updated by Gerrit Code Review almost 9 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46162

Actions #4

Updated by Gerrit Code Review almost 9 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/46162

Actions #5

Updated by Hannes Lau over 8 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by Gerrit Code Review over 8 years ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/47125

Actions #7

Updated by Hannes Lau over 8 years ago

  • Status changed from Under Review to Resolved
Actions #8

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF