Issue Task Resolved

#111316Use page ancestry for TSconfig, page tree, preview and module rootlines

Benni Mack 11/01/26, 19:44 updated 11/09/26, 09:45

Description

Following #111307, further callers of BackendUtility::BEgetRootLine() use the PageAncestryResolver, which resolves the ancestry of a page with one query instead of one query per page level.

Callers which already requested the workspace overlay:

  • PageTsConfigIncludesController and PageTsConfigActiveController
  • TemplateRecordsOverviewController
  • TreeController (mount point path)
  • PreviewController (draft version URL)
  • PageTreeRepository (filtering pages on mount points)
  • BackendUserAuthentication::initializeDbMountpointsInWorkspace(), now using the workspace of the user object instead of the global backend user
  • BackendLayoutView

The following callers did not apply the workspace overlay before and now resolve the ancestry in the workspace of the backend user, so moved pages in a workspace are taken into account:

  • SiteConfigurationController
  • AbstractTemplateModuleController (preview button, closest page with a template record)
  • PageInformationController and TranslationStatusController (preview links)

PageTsConfigRecordsOverviewController lists live pages only and keeps resolving the live ancestry.

Reviews 1

History 15

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

    Applied in changeset commit:cfad070081607cf0c66401c931e105acac62d588.