Issue Bug Closed

#110136"New pages" permission not cascading correctly anymore

Johann Allgäuer 07/01/26, 13:19 updated 08/11/26, 08:50

Description

We usually have the following page-permission setup for our editor backend usergroup:
- Root page has no “New pages” permission for the group
- All pages below do have a “New pages” permission for the group

See the attached screenshot.

In the current Version TYPO3 14.3.4, this leads to an error when an editor tries to create a new page below any of those pages, even below pages where the “New pages” permission is given.
Specifically, the “new page”-wizard errors out with the message “Failed to fetch available page types. This is likely due to missing permissions.”. Internally, the wizard/page/doktypes route (PageWizardController->getDoktypesAction) returns a 403 response.

In earlier TYPO3 versions this worked fine (even in 14.3.1).
We have used this kind of permission structure in multiple projects over the years, so it seems like an regression to me.

I would expect it to error out, when an editor tries to create a new page directly below the root page (where there is no “New pages” permission given)
I would expect it to work, when an editor tries to create a new page on any other page (where the “New pages” permission is given)

Adding the “New pages” permission to the root page fixes it, but we would like to keep the restriction for editors and not allow them to create pages directly below the root page.

Reviews 2

Files 1

History 79

  1. Benni Mack commented <span data-processor="relativetime" data-value="2026-08-06T16:29:32+00:00" > 08/06/26, 16:29 </span>

    The regression comes from commit 8c7ce3e8e1f (“[TASK] Add permission checks to PageWizardController”, #109324, backported into 14.3.x). It guards getDoktypesAction() with BackendUtility::readPageAccess($parentPageUid, $backendUser->getPagePermsClause(Permission::PAGE_NEW)) — but readPageAccess() doesn’t only check the given permission on the target page. It also verifies the page is inside a webmount, and that webmount check applies the same perms clause to every page in the rootline. So the “New pages” permission is effectively required on the whole ancestor chain up to the webmount, not just on the parent page.

  2. Benni Mack commented and changed status New Accepted Sprint Focus On Location Sprint <span data-processor="relativetime" data-value="2026-08-06T16:30:35+00:00" > 08/06/26, 16:30 </span>

    How to solve it: Use the pattern the rest of the core uses (e.g. NewRecordController, typo3/sysext/backend/Classes/Controller/NewRecordController.php:93,115,123): read the page with the PAGE_SHOW clause (show permission legitimately cascades through the rootline), then check the page-local “New pages” permission on the record itself:

    $parentPage = BackendUtility::readPageAccess((int)$parentPageUid, $backendUser->getPagePermsClause(Permission::PAGE_SHOW));
    if (!$parentPage || !$backendUser->doesUserHaveAccess($parentPage, Permission::PAGE_NEW)) {
    return new JsonResponse(null, 403);
    }

    doesUserHaveAccess() evaluates perms_userid/groupid/everybody on that single row, so the root page’s missing “New pages” bit no longer poisons descendants, while creating a page directly below the root still correctly 403s. (One edge worth covering: insertPosition !== ‘inside’ on a page directly under the root resolves $parentPageUid to 0 — non-admins get 403 there, which matches your expectation.

  3. Gerrit Code Review pushed patch set 1 for main to change 95151 status Accepted Under Review <span data-processor="relativetime" data-value="2026-08-06T21:22:19+00:00" > 08/06/26, 21:22 </span>

  4. René Pflamm commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-08-10T16:05:10+00:00" > 08/10/26, 16:05 </span>

    Applied in changeset commit:361993a2f65ace473291c101451277c8717e8974.