Review 14.3 Merged

95594[BUGFIX] Avoid PHP error on unresolvable page layout

Stefan Bürk CR +2 V +2 Easy +28 −1 updated 09/03/26, 09:14

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 +2 Done
    • Stefan Bürk +2
  • Verified V +2 Done
    • Stefan Bürk +2
    • core-ci +1 CI

Issues 1

Files 2

Review log 34

  1. Stefan Bürk uploaded patch set 1 09/03/26, 09:05

  2. core-ci voted on patch set 1 V +1 09/03/26, 09:13 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/107731

  3. Stefan Bürk voted on patch set 1 CR +2 V +2 09/03/26, 09:14

  4. Stefan Bürk merged patch set 2 09/03/26, 09:14