#100363Using a PropagateResponseException (for 404) in controller action displays Fluid error instead of 404 page since v12
Description
I am using this code in an Extbase show controller action to propagate the configured 404 page when a particular condition in the given model is not matched:
$response = GeneralUtility::makeInstance(ErrorController::class)->pageNotFoundAction(
$this->request,
'The requested product does not exist',
[
'code' => PageAccessFailureReasons::PAGE_NOT_FOUND,
],
);
throw new PropagateResponseException($response, 1615293813);
This works like expected in TYPO3 v11.5: The 404 page configured in the site configuration is displayed.
However, with v12.3 the following error is displayed instead of the 404 page:
Tried resolving a template file for controller action "Show->show" in format ".html", but none of the paths contained the expected template file (Show/Show.html). The following paths were checked: /var/www/html/vendor/myvendor/site/Resources/Private/Templates/Page/
with status code 500.
It looks like the subrequest(?) wants to use the Show template of the action for some reason (and looks for it in the folder for the page templates).
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 4
-
Benni Mack changed target version 06/05/23, 09:21
-
Benni Mack commented and changed status
NewNeeds Feedback 07/03/23, 18:05 -
Torben Hansen commented 07/06/24, 11:31
I’m not able to reproduce to problem. Works for me in v12 and v13.
-
Riccardo De Contardi commented and changed status
Needs FeedbackClosed target version 07/07/24, 17:16I think it’s safe to close this issue as solved (comment 3)
If you think that this is the wrong decision or experience the issue again, please reopen it or ping me on Slack and I’ll do it.Thank you.
I guess you’d rather want a ImmediateResponseException?