Issue Task Resolved

#111373Resolve backend page context, site and previews along the page ancestry

Benni Mack 11/09/26, 10:16 updated 11/09/26, 20:55

Description

Following #111307 and #111316, further callers of BackendUtility::BEgetRootLine() use the PageAncestryResolver. They resolve the ancestry of a page with one query, cached for the request, in the workspace of the backend user. Before, they resolved the live rootline, ignoring pages moved in a workspace.

  • PageContext keeps the PageAncestry of the page instead of a rootline array, the PageContextFactory resolves it.
  • The backend SiteResolver middleware resolves the site along the same ancestry, so the site and the page context share one query.
  • PreviewUriBuilder resolves the ancestry of the previewed page itself, before the BeforePagePreviewUriGeneratedEvent is dispatched. Callers no longer need to hand in a rootline: ImportController, NewRecordController, NewMultiplePagesController, SortSubPagesController, ElementInformationController, LanguageColumn, LatestChangedPagesWidget, PageLayoutController and RecordListController. getPreviewPageId() evaluates Page objects, so a page deleted in the workspace is detected.
  • TreeController (rootline of a page), RecordBreadcrumbProvider and the entry points of PageTreeRepository use the ancestry as well.

Reviews 1

History 13

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-09T20:55:13+00:00" > 11/09/26, 20:55 </span>

    Applied in changeset commit:80a27111063083358b18f5163df8917adbf227bd.