TYPO3 Logo
TYPO3 Core Changelog
Options
Give feedback View source How to edit Edit on GitHub Full documentation (single file)

TYPO3 Core Changelog

  • ChangeLog v14
    • 14.0 Changes
    • 14.x Changes by type
  • ChangeLog v13
    • 13.4.x Changes
    • 13.4 Changes
    • 13.3 Changes
    • 13.2 Changes
    • 13.1 Changes
    • 13.0 Changes
    • 13.x Changes by type
  • ChangeLog v12
    • 12.4.x Changes
    • 12.4 Changes
    • 12.3 Changes
    • 12.2 Changes
    • 12.1 Changes
    • 12.0 Changes
    • 12.x Changes by type
  • ChangeLog v11
    • 11.5.x Changes
    • 11.5 Changes
    • 11.4 Changes
    • 11.3 Changes
    • 11.2 Changes
    • 11.1 Changes
    • 11.0 Changes
    • 11.x Changes by type
  • ChangeLog v10
    • 10.4.x Changes
    • 10.4 Changes
    • 10.3 Changes
    • 10.2 Changes
    • 10.1 Changes
    • 10.0 Changes
    • 10.x Changes by type
  • ChangeLog v9
    • 9.5.x Changes
    • 9.5 Changes
    • 9.4 Changes
    • 9.3 Changes
    • 9.2 Changes
    • 9.1 Changes
    • 9.0 Changes
    • 9.x Changes by type
  • ChangeLog v8
    • 8.7.x Changes
    • 8.7 Changes
    • 8.6 Changes
    • 8.5 Changes
    • 8.4 Changes
    • 8.3 Changes
    • 8.2 Changes
    • 8.1 Changes
    • 8.0 Changes
    • 8.x Changes by type
  • ChangeLog v7
    • 7.6.x Changes
    • 7.6 Changes
    • 7.5 Changes
    • 7.4 Changes
    • 7.3 Changes
    • 7.2 Changes
    • 7.1 Changes
    • 7.0 Changes
    • 7.x Changes by type
  • Documenting Changes
  • Sitemap
  1. TYPO3 Core Changelog
  2. ChangeLog v12
  3. 12.3 Changes
  4. Deprecation: #100237 - TypoScript-related exceptions
Give feedback Edit on GitHub

Deprecation: #100237 - TypoScript-related exceptions

See forge#100237

Description

Two exception classes related to the TypoScript condition matching logic have been marked as deprecated in TYPO3 v12 and will be removed in v13:

  • \TYPO3\CMS\Core\Exception\MissingTsfeException
  • \TYPO3\CMS\Core\Configuration\TypoScript\Exception\InvalidTypoScriptConditionException

Impact

Both exceptions should have been marked @internal within the core, but were not.

The exception \TYPO3\CMS\Core\Exception\MissingTsfeException was an internal communication class and was caught internally, the use case was solved in a more simple way avoiding the exception.

The exception \TYPO3\CMS\Core\Configuration\TypoScript\Exception\InvalidTypoScriptConditionException was related to conditions which triggered a warning within the symfony expression language. Those were turned into this exception in TYPO3 v11. In TYPO3 v12, the original exception will bubble up, forcing developers to fix the broken Symfony condition syntax.

Affected installations

Third-party extensions most likely neither throw nor catch these exceptions, the extension scanner will find possible usages.

Migration

No direct migration available.

Note

Using the getTSFE() function, developers have to ensure that "TSFE" is available before accessing its properties. A missing "TSFE", e.g. in backend context, does no longer automatically evaluate the whole condition to FALSE. Instead, the function returns NULL, which can be checked using either [getTSFE() && getTSFE().id == 42] or the null-safe operator [getTSFE()?.id == 42].

  • Previous
  • Next
Reference to the headline

Copy and freely share the link

This link target has no permanent anchor assigned. You can make a pull request on GitHub to suggest an anchor. The link below can be used, but is prone to change if the page gets moved.

Copy this link into your TYPO3 manual.

  • Home
  • Contact
  • Issues
  • Repository

Last rendered: May 07, 2025 12:11

© since 1997 by the TYPO3 contributors
  • Legal Notice
  • Privacy Policy