Issue Bug Closed

#110475mod.SHARED.colPos_list and mod.web_layout.hideRestrictedCols have no effect in the page module

Hamada Saidi 08/13/26, 13:45 updated 08/25/26, 08:56

Description

## Summary

`mod.SHARED.colPos_list` and `mod.web_layout.hideRestrictedCols` are silently
ignored by the page module in v14. Both are read with dotted array keys from a
PageTSconfig array that has already had its dots removed, so both always fall
back to their defaults. Worked in v13.

## Steps to reproduce

1. Define a backend layout via PageTSconfig with an extra column, e.g. colPos 999.
2. Add to PageTSconfig:

mod.SHARED.colPos_list = 0,1,2
mod.web_layout.hideRestrictedCols = 1

3. Open the page module on a page using that layout.

Expected: the colPos 999 column is not rendered.
**Actual:** it is rendered as a normal, fully usable column, including its
“Create new content” button. Removing any other colPos from the list (e.g.
`0,1` to drop the footer column) also has no effect, which shows the setting is
never read rather than mis-evaluated.

## Cause

`PageContextFactory` stores the PageTSconfig array without dots:

// typo3/sysext/backend/Classes/Context/PageContextFactory.php:161
pageTsConfig: GeneralUtility::removeDotsFromTS(BackendUtility::getPagesTSconfig($pageId)),

`PageLayoutController` passes that array on:

// typo3/sysext/backend/Classes/Controller/PageLayoutController.php:281
$configuration = DrawingConfiguration::create($backendLayout, $this->pageContext->pageTsConfig, $viewMode);

`DrawingConfiguration::create()` reads it back with dots:

// typo3/sysext/backend/Classes/View/Drawing/DrawingConfiguration.php:85,87
$obj->shouldHideRestrictedColumns = (bool)($pageTsConfig[‘mod.’][‘web_layout.’][‘hideRestrictedCols’] ?? false);
$allowedColumnPositionsByTsConfig = array_unique(GeneralUtility::intExplode(‘,’, (string)($pageTsConfig[‘mod.’][‘SHARED.’][‘colPos_list’] ?? ‘’), true));

`[‘mod.’]` cannot exist in a dot-free array, so `hideRestrictedCols` is always
`false` and `colPos_list` is always `’‘`. The latter yields an empty array, which
takes the “no restriction” branch and sets `activeColumns` to every column in the
layout.

`DrawingConfiguration` is the only consumer of both settings in the page module,
so they are effectively dead configuration in v14.

## Inconsistency

`AbstractContentPagePositionMap` still reads both correctly, because it calls
`BackendUtility::getPagesTSconfig()` itself and gets the dotted array:

// typo3/sysext/backend/Classes/Tree/View/AbstractContentPagePositionMap.php:135,298
$hideRestrictedColumns = (bool)(BackendUtility::getPagesTSconfig($pid)[‘mod.’][‘web_layout.’][‘hideRestrictedCols’] ?? false);
$sharedColPosList = trim(BackendUtility::getPagesTSconfig($pageId)[‘mod.’][‘SHARED.’][‘colPos_list’] ?? ‘’);

So the position map honours the restriction while the page module does not.

## Suggested fix

Use dot-free keys in `DrawingConfiguration::create()`:

$obj->shouldHideRestrictedColumns = (bool)($pageTsConfig[‘mod’][‘web_layout’][‘hideRestrictedCols’] ?? false);
$allowedColumnPositionsByTsConfig = array_unique(GeneralUtility::intExplode(‘,’, (string)($pageTsConfig[‘mod’][‘SHARED’][‘colPos_list’] ?? ‘’), true));

Since the method is public API, it may be worth accepting either format, or
normalising at the call site instead.

## Affected

Confirmed on 14.3.6. Works as documented in 13.

Reviews 0

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

History 3