Duplicate Backend Layout Identifiers in Page TSconfig – Missing Uniqueness Check

Resolving Duplicate Layout Identifiers

In TYPO3 10 and 11 LTS, the Page TSconfig parser does not enforce uniqueness for keys under mod.web_layout.BackendLayouts. If multiple definitions use the same identifier, the last one processed silently overwrites all previous entries. This results in a dropdown that appears correct but renders columns based on the final definition, making it difficult to debug in complex, multi-extension environments.

Detection and Identification

Because the overwriting happens during the merge process, standard TSconfig viewing tools may not highlight the conflict. Use these steps to identify duplicates:

• Inspect Compiled TSconfig: Run the following command to rebuild the compiled configuration:

  vendor/bin/typo3cms typo3:tsc:compile

  Review the resulting files in typo3temp/tsconfig/compiled/. While the final array will only show the winner, comparing the source page.tsconfig files across extensions will reveal the duplicates.
• Manual Audit: Search your codebase for all occurrences of mod.web_layout.BackendLayouts to ensure no two extensions or configuration files use the same key.

Runtime Enforcement and Validation

TYPO3 does not currently provide a built-in uniqueness validator for backend layouts similar to the Site Configuration system. To enforce this at runtime, you can implement a custom check via a backend hook or a scheduled task.

Implementation via Hook

You can intercept the layout retrieval process to log warnings when conflicts are detected. Add a hook to ext_localconf.php targeting the layout utility:

$GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['backend/layout/BackendLayoutUtility.php']['getBackendLayouts'][] = \MyVendor\MyExtension\Hooks\BackendLayoutHook::class . '::checkDuplicates';

In the hook class, compare the keys of the loaded layouts. If the count of unique keys differs from the expected count of definitions (if tracked), or if you are iterating through raw TSconfig arrays, log the duplication to the TYPO3 system log using GeneralUtility::log().

Deployment Validation

Integrate a custom PHP script into your CI/CD pipeline that parses all page.tsconfig files. The script should load the files, simulate the merge, and throw an error if the same key is encountered more than once before the application is deployed to production.

Future Outlook

As of current versions, there is no official roadmap item to bring Site Configuration-style validation to Page TSconfig layouts. Validation remains the responsibility of the integrator through external linting or custom extension hooks.

Diagnostic Requirement

To provide a more specific automated script, please specify if you are using a custom BackendLayoutProvider or if your layouts are defined exclusively via TSconfig.