#100096extendToSubpages has no effect for subpages in menus
Description
In an instance that has been updated from TYPO3 10.4.36 to 11.5.24, subpages of an access protected page with the extendToSubpages option enabled are still visible in a frontend menu. This bug occurred once in TYPO3 9.5.12 and has been resolved, see #89989.
backend pagetree example:
- Root
- Public
- Secure (Usergroup Access Rights: usergroup, Extend to Subpages: enabled, Page enabled in menus: disabled)
- Mainmenu Parentpage (Usergroup Access Rights: Show at any login, Extend to Subpages: enabled, Page enabled in menus: disabled) <<< {$mainmenuPid}
- Subpage 1 (Page enabled in menus: enabled)
- Subpage 2 (Page enabled in menus: enabled)
- Sub Subpage 2 (Page enabled in menus: enabled)
…
- Sub Subpage 2 (Page enabled in menus: enabled)
- Mainmenu Parentpage (Usergroup Access Rights: Show at any login, Extend to Subpages: enabled, Page enabled in menus: disabled) <<< {$mainmenuPid}
menu processor:
page.10.dataProcessing.30 = TYPO3\CMS\Frontend\DataProcessing\MenuProcessor
page.10.dataProcessing.30 {
special = directory
special.value = {$mainmenuPid}
levels = 4
expandAll = 1
includeSpacer = 1
titleField = nav_title // title
as = mainmenu
}
To hide the subpages of “Mainmenu Parentpage”, an “Usergroup Access Rights” item needs to selected. The visibility of the subpages should be taken over from the parent page by extendToSubpages.
Reviews 2
History 412
-
Sebastian Klein commented <span data-processor="relativetime" data-value="2023-04-12T13:55:28+00:00" > 04/12/23, 13:55 </span>
-
Benni Mack changed Sprint Focus Stabilization Sprint <span data-processor="relativetime" data-value="2023-06-06T13:13:45+00:00" > 06/06/23, 13:13 </span>
-
Patrick Lenk changed target version TYPO3 Version
1112 <span data-processor="relativetime" data-value="2024-10-29T10:08:02+00:00" > 10/29/24, 10:08 </span> -
Gerrit Code Review pushed patch set 1 for main to change 88652 status
NewUnder Review <span data-processor="relativetime" data-value="2025-03-19T17:08:30+00:00" > 03/19/25, 17:08 </span> -
Gerrit Code Review pushed patch set 2 for main to change 88652 <span data-processor="relativetime" data-value="2025-04-02T06:25:24+00:00" > 04/02/25, 06:25 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 88652 <span data-processor="relativetime" data-value="2026-04-22T06:30:06+00:00" > 04/22/26, 06:30 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 88652 <span data-processor="relativetime" data-value="2026-11-01T17:47:43+00:00" > 11/01/26, 17:47 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 88652 <span data-processor="relativetime" data-value="2026-11-06T09:27:45+00:00" > 11/06/26, 09:27 </span>
-
Gerrit Code Review pushed patch set 1 for 14.3 to change 97400 <span data-processor="relativetime" data-value="2026-11-06T20:46:33+00:00" > 11/06/26, 20:46 </span>
-
Gerrit Code Review pushed patch set 2 for 14.3 to change 97400 <span data-processor="relativetime" data-value="2026-11-06T20:50:05+00:00" > 11/06/26, 20:50 </span>
-
Gerrit Code Review pushed patch set 3 for 14.3 to change 97400 <span data-processor="relativetime" data-value="2026-11-06T21:28:52+00:00" > 11/06/26, 21:28 </span>
-
Georg Ringer commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-11-06T22:15:10+00:00" > 11/06/26, 22:15 </span>Applied in changeset commit:a05d0a1813cfa167b613cd4f43085947f7aad608.
We have a similar page tree setup in TYPO3 v11 and can confirm the issue.