Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUGFIX: Set templatePathAndFilename for serverErrorExceptions to prevent "Template not found" #15

Merged
merged 1 commit into from
Jun 19, 2023

Conversation

paxuclus
Copy link
Member

@paxuclus paxuclus commented May 31, 2023

useCustomErrorView() of the AbstractExceptionHandler only checks if the array key templatePathAndFilename is set, but not if it's a valid string. This means that setting templatePathAndFilename to null will cause an exception during exception rendering, hiding the original error.

This only affects Development, as our own implementation of the ProductionExceptionHandler always returns false for useCustomErrorView().

…ent "Template not found"

useCustomErrorView() of the AbstractExceptionHandler only checks if the array key
templatePathAndFilename is set, but not if it's a valid string. This means that
setting templatePathAndFilename to null will cause an exception during exception
rendering, hiding the original error.
@paxuclus paxuclus added the bug Something isn't working label May 31, 2023
@paxuclus paxuclus requested a review from toni-bessel May 31, 2023 08:00
@paxuclus paxuclus self-assigned this May 31, 2023
@paxuclus paxuclus merged commit afe14f9 into master Jun 19, 2023
@paxuclus paxuclus deleted the bugfix/template-not-found branch June 19, 2023 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging this pull request may close these issues.

None yet

2 participants