Issue Bug Under Review Quiet

#110596PAGEVIEW fails with PHP error when page layout can not be resolved

Stefan Bürk 09/02/26, 09:59 updated 10/15/26, 08:18

Description

Problem

The data processor “page-content” fetches the content areas of the
current page layout. It reads them with a null safe call, but then uses
the result twice without a guard:

bc. $contentAreas = $pageInformation->getPageLayout()?->getContentAreas();

The following two lines call getGroupedRecords and withUpdatedRecords on
that variable. If the page layout could not be resolved, the variable is
null and the request dies with

bc. Error: Call to a member function getGroupedRecords() on null

When the page layout is null

PageLayoutResolver returns null whenever a layout identifier was
resolved for the page, but the definition for that identifier can not be
found for the page id. The synthesised “default” identifier always
resolves, so this needs a page which references a named layout whose
definition is missing in the context of that page.

A reported real world case: a mount point with mount overlay enabled,
whose target page lives in a different site, using page TSconfig based
backend layouts. Rendering the mounted page through PAGEVIEW ends in the
error above. The user worked around it with an own data processor which
catches the error.

Effect

An unresolvable page layout takes down the whole frontend request with a
PHP error instead of rendering the page. Rendering through the classic
CONTENT chain is not affected, because it never asks for a page layout.

Expected

The processor must not fail with a PHP error. With no resolvable page
layout it should provide an empty set of content areas, so the page
still renders and the template can decide what to do.

Affected code

typo3/sysext/frontend/Classes/DataProcessing/PageContentFetchingProcessor.php

Same code in main, 14.3 and 13.4. There is no test for a page without a
resolvable page layout.

Reviews 6

History 26

  1. Stefan Bürk commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-09-03T09:15:10+00:00" > 09/03/26, 09:15 </span>

    Applied in changeset commit:8ad52714d35e6fd1d5d9f1970e76e87a3db13d21.

  2. Gerrit Code Review pushed patch set 1 for 13.4 to change 96711 status Resolved Under Review <span data-processor="relativetime" data-value="2026-10-15T08:18:01+00:00" > 10/15/26, 08:18 </span>