Issue Feature New Orphaned

#91504Subpages of pages with access setting "extendToSubpages" should be able to override this settings

Alessandro Schmitz 05/27/20, 11:04 updated 06/28/22, 13:47

Description

Quite a bit complicated to explain but I’ll try:

Example Pagetree:

.
├── Page Level 1 A (Usergroups: A and B - ExtendToSubpages: true)
│   ├── Subpage Level 2 A
│   ├── Subpage Level 2 B (Usergroups: A, B and C - ExtendToSubpages: true)
│   │   ├── Subpage Level 3 A
│   │   └── Subpage Level 3 B
│   └── Subpage Level 2 C
└── Page Level 1 B (Usergroups: C - ExtendToSubpages: true)

I would expect that “Subpage Level 2 B” overrides the accessibility of “Page Level 1 A”. So “Subpage Level 2 B” should be accessible by usergroups A,B and C. Usergroup C would need a deep link somewhere, as “Page Level 1 A” won’t show up in menu.

The current behavior would be a “403 Page Not Found – Reason: Subsection was found and not accessible” if you access “Subpage Level 2 B” with usergroup C.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[FEATURE] Subpages of pages with access setting "extendToSubpages" should be able to override this settings Resolves: #91504 Releases: main