Bug #81190

rtehtmlarea: TSconfig with page based condition is ignored in BrowseLinks and SelectImage windows

Added by Marc Bastian Heinrichs over 3 years ago. Updated over 2 years ago.

Should have
RTE (rtehtmlarea + ckeditor)
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


  • You have a multi tree instance with different RTE TSconfigs per tree.
  • You want to avoid references to the TSconfig files in page records.
  • So you use conditions with including the tsconfig in ext_localconf like this:
        '<INCLUDE_TYPOSCRIPT: source="FILE:EXT:foo/Configuration/TsConfig/Page/page_base.ts" condition="[PIDinRootline = 1234]">'

The TSconfig is totally ignored in the BrowseLinks and SelectImage windows loaded in an iframe.

The ConditionMatcher instantiated by the TypoScriptParser tries to determine the page using GetVars 'id', 'edit' or 'cmd'. Those vars are not used loading the iframes, but a special string called 'RTEtsConfigParams'. So no page id, so no rootline to be evaluated for the condition.

Include GetVar 'id' with the page uid into the iframe url.

I did not checked (yet) if v8 has a similar bug with ckeditor.

Related issues

Related to TYPO3 Core - Bug #81853: TSconfig with page based condition is ignored using page tree commands and clipboardNew2017-07-13


Updated by Gerrit Code Review over 3 years ago

  • Status changed from New 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/52756


Updated by Riccardo De Contardi over 3 years ago

I have performed the following test with TYPO3 7.6.18:

1) use the standard RTEHtmlarea config

2) load a TSConfig file only for a specific pagetree:

ext_localconf of my extension:

    '<INCLUDE_TYPOSCRIPT: source="FILE:EXT:bhsiteconf/Configuration/TypoScript/TSconfig/Test/test.ts" condition="[PIDinRootline = 44]">'

2) file test.ts:

    showButtons = *

RTE.classesAnchor {
   externalLink {
      class = external-link
      type = url
      altText = TESTE
      titleText = TESTE
   externalLinkInNewWindow {
      class = external-link-new-window
      type = url
      altText = TESTENW
      titleText = TESTENW
   internalLink {
      class = internal-link
      type = page
      altText = TESTI
      titleText = TESTI
   internalLinkInNewWindow {
      class = internal-link-new-window
      type = page
      altText = TESTINW
      titleText = TESTINW
   download {
      class = download
      type = file
      altText = TESTD
      titleText = TESTD
   mail {
      class = mail
      type = mail
      altText = TESTM
      titleText = TESTM


The "new" name for the link classes are loaded for the subpages of page 44

Is this test sufficient or a more complete test should be performed?


Updated by Marc Bastian Heinrichs over 3 years ago

Hey Riccardo, thx for testing. I can not confirm your test. Still buggy for me in 7.6.18.

The problematic code starts here
The TypoScriptParser has no idea about the page id, so the BackendConditionMatcher created here
could not be feed with the page id, like here

So the BackendConditionMatcher uses its function determinePageId to get the page id.


Updated by Marc Bastian Heinrichs over 3 years ago

  • Related to Bug #81853: TSconfig with page based condition is ignored using page tree commands and clipboard added

Updated by Marc Bastian Heinrichs over 3 years ago

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

Updated by Benni Mack over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF