TYPO3 Core

quick investigation:

This is likely caused by https://review.typo3.org/c/Packages/TYPO3.CMS/+/84945
Since that change PageDoktypeRegistry became a service that requires DI.

I would have said, that the ext_tables.php check needs to use LateBootService and boot a container, but it should already do that in typo3/sysext/install/Classes/Service/LoadTcaService.php – so I don't know the exact reason right now.

Needs to be checked manually…

CC @Oliver Bartsch

Please share the exact contents of the ext_tables.php files.

Could not verify with v13.2.1 having a ext_tables.php with:

<?php
use TYPO3\CMS\Core\DataHandling\PageDoktypeRegistry;
use TYPO3\CMS\Core\Utility\GeneralUtility;
$dokTypeRegistry = GeneralUtility::makeInstance(PageDoktypeRegistry::class);

Here is content of my ext_tables.php file:

<?php
declare(strict_types=1);

use TYPO3\CMS\Core\DataHandling\PageDoktypeRegistry;
use TYPO3\CMS\Core\Utility\GeneralUtility;

defined('TYPO3') or die();

(function () {
    /**
     * Register doktype 110 for article pages
     */
    $articlePageDoktype = 110;

    $dokTypeRegistry = GeneralUtility::makeInstance(PageDoktypeRegistry::class);
    $dokTypeRegistry->add(
        $articlePageDoktype,
        [
            'type' => 'web',
            'allowedTables' => '*',
        ],
    );
})();