Actions
Bug #78825
closed
Wrong pid determination when opening a nested access restriced page
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2016-11-28
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
Given the tree from the attached image:
- The 'Users' folder contains a Website Group and User
- 'Access Page' is a child of 'Folder'
- 'Access Page' is only accessible by users that have that group and 'Extend to Subpages' is enabled in the Access tab
When a frontend user tries to open the page 'Page', which is access restricted by its parent page, TYPO3 looks for the next accessible page which ends up being 'Folder' instead of 'Home'.
When opening 'Access Page' it works as expected and 'Home' gets displayed.
Files
Updated by Sorin Loghin over 7 years ago
- Subject changed from Wrong pid determination when previewing a page inside a folder to Wrong pid determination when previewing a nested access restriced page
Updated by Sorin Loghin over 7 years ago
- Subject changed from Wrong pid determination when previewing a nested access restriced page to Wrong pid determination when opening a nested access restriced page
Updated by Riccardo De Contardi about 7 years ago
can this be considered a duplicate of #15984 ? See https://forge.typo3.org/issues/15984#note-15
Updated by Riccardo De Contardi about 7 years ago
- Related to Bug #15984: menu.showAccessRestrictedPages doesn't replace link for "include subpages" added
Updated by Riccardo De Contardi about 7 years ago
- Related to Bug #26484: extend to subpages in page properties in access tab does not work correctly added
Updated by Susanne Moog about 4 years ago
- Status changed from New to Needs Feedback
Can you recheck on a current version if the changes in site handling and routing fixed the issue?
Updated by Christian Kuhn about 2 years ago
- Status changed from Needs Feedback to Closed
hey. i hope it's fair enough to close here for now: i think this issue has probably been fixed meanwhile, and the reporter didn't call back for quite a while. let's restart with a fresh issue in case there are still problems.
Actions