[Issue] improve exception handling in Layout render #29606
Labels
Component: View
Fixed in 2.4.x
The issue has been fixed in 2.4-develop branch
Issue: Confirmed
Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed
Issue: Format is valid
Gate 1 Passed. Automatic verification of issue format passed
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
Priority: P2
A defect with this priority could have functionality issues which are not to expectations.
Reproduced on 2.4.x
The issue has been reproduced on latest 2.4-develop branch
Severity: S3
Affects non-critical data or functionality and does not force users to employ a workaround.
This issue is automatically created based on existing pull request: #27478: improve exception handling in Layout render
Preconditions (*)
When layout is being rendered in production mode, all exception messages are logged to system log as critical issues. However exception stack is lost. If we pass exception to
LoggerInterface::critical
instead this data will be saved tovar/report
.Steps to reproduce (*)
throw \Exception('test');
in a template.var/report
in addition to its message being logged.Actual Result: (*)
✖️ All exception messages are logged to system log
Expected Result:
✔️ Messages should be logged to the exception log file
Questions or comments
Exception
toLoggerInterface::critical
a preferred way of logging issues? (I see it being used this way in other places)LocalizedException
adding any value?Contribution checklist (*)
The text was updated successfully, but these errors were encountered: