Review 13.4 Abandoned

96711[BUGFIX] Avoid PHP error on unresolvable page layout

Garvin Hicking CR 0 V 0 Easy +36 −0 updated 10/15/26, 08:18

Commit message

The "page-content" data processor read the content areas of
the current page layout with a null safe call, but then used
the result without a guard. Whenever the page layout did not
resolve, the frontend request died with

  Call to a member function getGroupedRecords() on null

A page layout does not resolve when a layout identifier is
found for a page while the definition for that identifier is
not available in the context of that page. A reported case is
a mount point with mount overlay, whose target page lives in
another site, using page TSconfig based backend layouts.

Fall back to an empty content area collection, so the page is
rendered instead of failing with a PHP error. Rendering via
the classic CONTENT chain never asked for a page layout and
was not affected.

Review

  • Code review CR 0
  • Verified V 0

Issues 1

Files 2

Review log 3

  1. Garvin Hicking commented on patch set 1 10/15/26, 08:17

    Cherry Picked from branch main. The following files contain Git conflicts: * typo3/sysext/frontend/Classes/DataProcessing/PageContentFetchingProcessor.php
  2. Garvin Hicking wrote 10/15/26, 08:18

    Topic set to #no-backport
  3. Garvin Hicking abandoned the change 10/15/26, 08:18

    won't do even though listed in Releases: