Issue Bug Resolved

#111327Page new in a workspace is outside the webmounts when checked from live

Benni Mack 11/03/26, 09:38 updated 11/07/26, 21:50

Description

Since #111307 (“Resolve page ancestry in the backend with one query”), BackendUserAuthentication::isInWebMount() checks a page along the ancestry resolved by the PageAncestryResolver when it is called without a permission clause. With a clause given, it still walks the page tree with BackendUtility::BEgetRootLine().

For a page that only exists in a workspace (new page, t3ver_state = 1), checked for a non-admin user in live, the two paths disagree:

  • isInWebMount($uid) returns null, as the live ancestry does not contain the page
  • isInWebMount($uid, $backendUser->getPagePermsClause(Permission::PAGE_SHOW)) returns the webmount, as BEgetRootLine() reads the page record regardless of the workspace

Before #111307 both calls walked the page tree with the clause and returned the webmount.

Steps to reproduce

  1. Page tree: Root (1) > Site A (2, webmount of the user) > Sub (3)
  2. In workspace 1, create a new page below Sub (e.g. uid 12, t3ver_wsid 1, t3ver_state 1)
  3. As a non-admin user in live: isInWebMount(12) returns null, isInWebMount(12, $backendUser->getPagePermsClause(1)) returns 2

Open question

Which result is intended? A page that does not exist in live is arguably not within a webmount in live, so the ancestry result may be the correct one. Then the walk with the clause should agree, and callers that check workspace records while being in live need a look.

Found while extracting the page permission checks for the authorization work (#111235). A functional test comparing both paths pins the difference.

Reviews 1

History 25

  1. Benni Mack commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-11-07T21:50:10+00:00" > 11/07/26, 21:50 </span>

    Applied in changeset commit:bfd20c6564662b7090a678be3c7380dbcd80b26c.