Issue Task New Orphaned

#108391Read default backend_layout from tsconfig if key is present

Soren Malling 12/03/25, 15:03 updated 12/04/25, 08:56

Description

I propose a change to the DefaultDataProvider for backend layouts.

Having a default backend layout for a project that is different from a single colPos, require you to either * create a backend_layout database entry * create a page.tsconfig with a key
and select that afterwards in “Page properties”.

This is due to the “DefaultDataProvider” looking if the key is “default” – and then fallback to a default tsconfig.

I suggest that the default provider can look at the tsconfig of the pageId given to “getBackendLayout” and can see if the “default” key is set. This could have been done via a configured site set.

And if set, use that configuration.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[TASK] Read default backend_layout from tsconfig if key is present Resolves: #108391 Releases: main

Files 2

History 3

  1. Soren Malling commented and changed attached Screenshot 2025-12-04 at 09.46.53.png <span data-processor="relativetime" data-value="2025-12-04T08:50:38+00:00" > 12/04/25, 08:50 </span>

    By request: Examples! Based on the EXT:bootstrap_package code :-D

    Say you have a site, with a default layout with multiple areas. For example, the bootstrap package provides this “default” layout

    https://github.com/benjaminkott/bootstrap_package/blob/96499c64fd8c603f11317db15eb62b1d54d6ff52/Configuration/Sets/BackendLayouts/PageTsConfig/BackendLayouts/default.tsconfig

    This is presented with the value “pagests__default”, shown in the image here.

    And the “default” being the one from DefaultDataProvider

    https://github.com/TYPO3/typo3/blob/eb20167e1cf0f4b74beec7efa3f1300db075a743/typo3/sysext/backend/Classes/View/BackendLayout/DefaultDataProvider.php#L40

    The improvment I see possible here, is to be able to override what is considered the “default” layout of my backend.

    As of now, a editor have to select a different “default”