Error reason not seen when 500 template is missing
| Reported by: |
wojtek@… |
Owned by: |
turkey |
|
Component:
|
contrib.admin
|
Version:
|
|
|
Severity:
|
normal
|
Keywords:
|
|
|
Cc:
|
|
Triage Stage:
|
Accepted
|
|
Has patch:
|
no
|
Needs documentation:
|
no
|
|
Needs tests:
|
no
|
Patch needs improvement:
|
no
|
|
Easy pickings:
|
no
|
UI/UX:
|
no
|
When DEBUG = False (production environment) and an error happens, and the 500 template is not provided - one gets a traceback about the template not existing, but does not get a traceback for the exception that caused the actual failure.
Change History
(11)
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
| Resolution: |
fixed
|
| Status: |
closed → reopened
|
| Resolution: |
→ wontfix
|
| Status: |
reopened → closed
|
| Resolution: |
wontfix
|
| Status: |
closed → reopened
|
| Owner: |
changed from Adrian Holovaty to turkey
|
| Status: |
reopened → new
|
| Resolution: |
→ fixed
|
| Status: |
new → closed
|
| Resolution: |
fixed
|
| Status: |
closed → reopened
|
| Triage Stage: |
Unreviewed → Accepted
|
| Resolution: |
→ wontfix
|
| Status: |
reopened → closed
|
I don't think that by default with errors off we should reveal internal implementation details.
One solution for this error template situation would be "last chance" template loader. This would just respond to the 400, 500, and template_debug template names, and would be last in the list of loaders ( maybe appended automatically to this list). It would load extremely simple templates from strings, meaning it only relies on python module loading.