Project

General

Profile

Actions

Bug #78825

closed

Wrong pid determination when opening a nested access restriced page

Added by Sorin Loghin over 7 years ago. Updated about 2 years ago.

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

Tree.png (6.94 KB) Tree.png Sorin Loghin, 2016-11-28 19:56

Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Bug #15984: menu.showAccessRestrictedPages doesn't replace link for "include subpages"Accepted2006-04-05

Actions
Related to TYPO3 Core - Bug #26484: extend to subpages in page properties in access tab does not work correctlyClosed2011-04-29

Actions
Actions

Also available in: Atom PDF