Project

General

Profile

Actions

Bug #100938

closed

Display of parent page not working if group access denies specific page

Added by Philipp Wrann over 1 year ago. Updated 10 months ago.

Status:
Closed
Priority:
-- undefined --
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2023-05-31
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
8.2
Tags:
pending-close
Complexity:
Is Regression:
Sprint Focus:

Description

TL;DR;

The TSFE->pageNotFound setting prevents the TSFE to display the unrestricted parent page if the requested page is limited to logged in users.

https://github.com/TYPO3/typo3/blob/f731cb6cc774fdf317e02be07e9cee9a35abd04c/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php#L806

Everything after the linked line is useless, because of pageNotFound NOT being "0" a PropagateResponseException is will always be thrown.

Full story:

see https://talk.typo3.org/t/access-to-page-with-fe-group-restriction-redirect-to-unresitricted-parent-not-working-in-v11/4860/1

After upgrading a typo3 installation to V11 it seems some default handling regarding the frontend authentication of the requested page did break. The expected behaviour for requesting access-restricted pages is, that the response will contain the first page found in the rootline which is not restricted. The actual behaviour is a 403 error page.

What is the correct migration to achieve the desired behaviour for typo3 v11?

My customer states that the behaviour was differently prior to the V11 upgrade but i can not find the change that causes the bug.

Actions

Also available in: Atom PDF