TYPO3 Core

How to test?¶

config.debug = 0

page = PAGE
page.stdWrap.parseFunc = 1

page.10 = TEXT
page.10 {
  value = Link
  typolink.parameter = / 200x300
}

page.20 = IMAGE
page.20 {
   file = fileadmin/introduction/images/unsplash/annie-spratt-604129-unsplash.jpg
   file.width = 80
   imageLinkWrap = 1
   imageLinkWrap {
      enable = 1
      JSwindow = 1
   }
}

page.30 = HMENU
page.30 {
  special = directory
  special.value = 1 // adjust to valid page ID having sub-pages
  JSWindow = 1
  1 = TMENU
  1.JSWindow = 1
  1.NO = 1
  1.NO {
    stdWrap.htmlSpecialChars = 1
  }
}

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/c/Packages/TYPO3.CMS/+/70551

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

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

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

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

Helmut Hummel wrote in #note-9:

page.stdWrap.parseFunc = 1

Do we really need to stay backwards compatible with something like that?

parseFunc = 1 is still a regular stdWrap functionality. In this example it is used to trigger HTML parser(!) and HTML sanitizer(!) - at the time of having created this issue, htmlSanitize = 1 was still enabled per default.

And if so, isn't that resolved with #94786 as html sanitize is now disabled by default?

No, htmlSanitize is disabled with #94786 when parseFunc gets called directly in TypoScript.

In case lib.parseFunc is used (e.g. stdWrap.parseFunc = < lib.parseFunc), htmlSanitize is still enabled when using ext:fluid_styled_content, see https://github.com/TYPO3/typo3/blob/v10.4.19/typo3/sysext/fluid_styled_content/Configuration/TypoScript/Helper/ParseFunc.typoscript#L44

Having htmlSanitize enabled per default in ContentObjectRenderer::parseFunc aimed to protect those scenarios that cleared their TypoScript libs, like lib.parseFunc > or lib.parseFunc_RTE >.

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

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

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