Actions
Bug #80813
closed
incorrect pageNotFound_handling behaviour
Start date:
2017-04-11
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
[FE][pageNotFound_handling] is empty per Default, which means requests for non-existing/accessible pages will be handled by linking upwards in the page tree.
If you create a page which is a "shortcut of first subpage", but has no subpages, a 404 exception is thrown instead of the upwards linking.
The configurations 'false' and '0' are also handled differently.
The behaviour for 'true' and '1' is correct.
Updated by Henrik Elsner about 7 years ago
- Related to Bug #78831: Page shortcut "first subpage of page" with no accessible subpages causes uncaught PageNotFoundException added
Updated by Henrik Elsner about 7 years ago
- Subject changed from pageNotFound_handling to incorrect pageNotFound_handling behaviour
Updated by Henrik Elsner about 7 years ago
- Status changed from Needs Feedback to In Progress
- Assignee set to Henrik Elsner
Updated by Riccardo De Contardi over 5 years ago
- Related to Bug #82036: Missing use of pageNotFound_handling in TypoScriptFrontendController.php, only PageNotFoundException is used. added
Updated by Benni Mack about 4 years ago
- Status changed from In Progress to Closed
PageNotFoundHandling options have been reworked in TYPO3 v9+. Shortcut to first subpage throws 404 is correct.
Actions