[DOCS] Add hint about "temp." TypoScript top-level object

[TYPO3IncTeam]

ℹ️ View this commit on Github
👥 Authored by Christian Kuhn [email protected]
✔️ Merged by Christian Kuhn [email protected]

Commit message

[DOCS] Add hint about "temp." TypoScript top-level object

Frontend TypoScript 'temp.' was removed after parsing
with the pre-v12 parser. The v12 parser does not do this
anymore. Unsetting 'temp.' never really made much
sense, and for instance had the side effects that
the object browser could never show it. We thus
decided to not add this special handling again, but
to document this subtle change instead.

Note 'styles.' had the same handling as 'temp.'
until v7, where its special handling was removed
without further impact.

Resolves: #105599
Related: #97816
Related: #60567
Releases: main, 13.4, 12.4
Change-Id: I5b2773317b7d69114bcc6da5d38439d93c633e34
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86986
Tested-by: Oliver Thiele [email protected]
Tested-by: Garvin Hicking [email protected]
Reviewed-by: Oliver Thiele [email protected]
Tested-by: Christian Kuhn [email protected]
Tested-by: core-ci [email protected]
Reviewed-by: Christian Kuhn [email protected]
Reviewed-by: Garvin Hicking [email protected]

➗ Modified files

12.0/Breaking-97816-TypoScriptSyntaxChanges.rst

@@ -313,5 +313,14 @@ a whitespace between :typoscript:`=` and :typoscript:`<`:
 
     lib.nav.wrap = <ul id="nav">|</ul>
 
+Frontend TypoScript `temp.` top level object
+--------------------------------------------
+
+The Frontend TypoScript related top level object :typoscript:`temp` had special
+functionality until v12: Any TypoScript defined within was "temporary" at parse time
+and unset afterwards. It was not cached and could not be used as reference
+(:typoscript:`=<` operator). This special meaning has been removed, the key
+:typoscript:`temp` now works just like any other top level key.
+
 
 .. index:: Backend, Frontend, TSConfig, TypoScript, NotScanned, ext:core