Feature #42135
Include technical details to exceptions in dev context
| Status: | Resolved | Start date: | 2012-10-18 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Bastian Waidelich | % Done: | 100% |
|
| Category: | Error | |||
| Target version: | TYPO3 Flow Base Distribution - 2.0 beta 1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | No |
Description
Since the implementation of custom error renderers (#39423) 404 errors don't show any technical details to the user, even in development context.
This should be changed, so we can include details about the resolved package key, controller name etc if no matching controller could be found.
Related issues
Associated revisions
[FEATURE] Include technical details to exceptions in dev context
Since the implementation of custom error renderers (#39423)
404 errors don't show any technical details to the user,
even in development context.
This change passes the exception to the fluid template which can
render it, if configured. Furthermore this adds default rendering
options and configures all exceptionHandlers to include technical
details in development context.
Change-Id: I79347ce49f38d417a7f3c2cc854e7c0a70a88ab8
Resolves: #42135
Releases: 1.2
History
#1 Updated by Karsten Dambekalns over 2 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Solved with https://review.typo3.org/15787