TYPO3 Core

The same error is triggered when an extension requests Page TSconfig for page with UID 0 (for whatever reason) like Grid Elements currently does: https://gitlab.com/coderscare/gridelements/-/issues/171

Just had the very same issue. I resolved it via declaring that constant globally (so it's also present on the root level)

From the docs we know the sequence of how the stack of constants is being put together:

The TypoScript constants are evaluated in this order:

• Global 'defaultTypoScript_constants'
• Site specific settings from the site configuration
• Constants from sys_template database records

So all I had to do is this in a ext_localconf.php:

        \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addTypoScript(
            'my_extension',
            'constants',
            '@import \'my_extension/Configuration/GlobalSettings.typoscript\''
        );

Cheerio ;-)

I solved this issue as well, albeit differently:

Instead of including TSConfig globally via ext_localconf.php :

ExtensionManagementUtility::addPageTSConfig('<INCLUDE_TYPOSCRIPT: source="DIR:EXT:my_extension/Configuration/TsConfig/Page">');

I just register main (bootstrap) file in Configuration/TCA/Overrides/pages.php :

ExtensionManagementUtility::registerPageTSConfigFile(
    'my_extension',
    'Configuration/TsConfig/Page/example_site.tsconfig',
    'Example site'
);

I then include the registered file on root page of the site it relates too. This way the TSConfig is not evaluated on global root page and there are no parsing errors.

Christian Kuhn wrote in #note-5:

Is there anything left to do for v12 and upwards?

Hallo Christian,

we have a work-around for TYPO3 10 and no problems with TYPO3 11 or newer, so I would say the issue can be closed.