-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] sub page of restricted page with "Extend to Subpages" is not indexed #3969
Comments
It seems this was introduced by this change and should therefore only affect v12 |
@deschilter There are 13 files changed, which part of change exactly? Is #3926 related? Could you try if that fixes the issue? |
The part which checks if the FrontendGroupsModifier should be applied. I tested #3926 and it does not solve this issue. |
Describe the bug
When a page is restricted to an
fe_group
by restricting the parent page and activating the "Extend to Subpages", it won't be indexed.The indexing request will result in a 404 and the
frontendHelper
is never called.This is because no or
pageUserGroup
is passed in the request.It is only passed if the current page is restricted: PageIndexer.php#L297
In that case the
FrontendGroupsModifier
would grant access to the page, but without auserGroup
or apageUserGroup
, it won't.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Both pages, parent and child, should be correctly indexed.
Currently only the parent is indexed and the child results in an error.
Used versions (please complete the following information):
The text was updated successfully, but these errors were encountered: