Bug #95174
closed
pageNotFoundAction not working properly in Extbase with feature toggle subrequestPageErrors turned on
100%
Description
When the feature toggle subrequestPageErrors is turned on, the subrequest does not properly fetch the configured page uid of the error handler and return an "empty" (just some basic TYPO3 HTML available) page instead.
How to reproduce:
Ensure that the TYPO3 page error handler is configured to show the content of a TYPO3 page and that that page contains some content to be shown.
The most easy way to reproduce the problem is to test it in TYPO3 core ext:felogin, which is an Extbase extension with a frontend plugin. Add the plugin "Frontend Login" to a page in the pagetree and open the page in the frontend. The login form should be shown.
Now in TYPO3\CMS\FrontendLogin\Controller\LoginController::loginAction add the following code to the start of the action:
$response = GeneralUtility::makeInstance(\TYPO3\CMS\Frontend\Controller\ErrorController::class)->pageNotFoundAction(
$this->request,
'Object not found.'
);
throw new \TYPO3\CMS\Core\Http\PropagateResponseException($response, 1631261423);
With subrequestPageErrors feature toggle turned off, the content of the configured error page is shown. When the feature flag is turned on, only a blank page is shown.
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by 
Updated by