| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002821 | Composr | core | public | 2016-09-10 21:24 | 2017-05-01 16:12 |
| Reporter | Patrick Schmalstig | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002821: More advanced error screens | ||||
| Description | Attached is a screenshot of how another content management system handles errors. I think it is very beautifully laid out, very intuitive and helpful, and something Composr could potentially benefit from. Synopsis: *The error is in the top left corner. There are links under the error that you can click to search google and Stack trace for details about the error. You can also copy error details to the clipboard. The clipboard contains the error message and the stack trace. *Under the error message on the left panel is the stack trace, displayed as a clickable stack. Clicking any of the items allows you to pull up some very useful dev information on the right side, such as a preview of the code and where the stack trace executed at, details about the user's environment and variables, session info, server/request data, environment variables, and registered handlers. | ||||
| Tags | Type: Usability (major) | ||||
| Time estimation (hours) | 7 | ||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-09-10 21:24 | Patrick Schmalstig | New Issue | |
| 2016-09-10 21:24 | Patrick Schmalstig | File Added: 49fc10cdb47464bd7fc32636606b145e.png | |
| 2016-09-12 15:25 | Chris Graham | Time estimation (hours) | => 7 |
| 2016-10-31 05:54 | Patrick Schmalstig | Note Added: 0004508 | |
| 2017-05-01 16:12 | Chris Graham | Tag Attached: Type: Usability (major) |