[patch] Error handlers lack context.
Which isn't nice because often one sets various extra_context variables for the views in the middleware. And the 404 view could be using a template which requires some variables from the context (for example name of the currently logged in user).
So it would be nice if page_not_found in django/views/defaults would pass the extra_context variables when rendering the 404.html template.
Change History
(19)
| Resolution: |
→ invalid
|
| Status: |
new → closed
|
| Cc: |
django@… added
|
| Keywords: |
errors handlers 404 500 added
|
| Resolution: |
invalid
|
| Status: |
closed → reopened
|
| Type: |
defect → enhancement
|
| Summary: |
Default 404 handler uses no context. → [patch] Error handlers lack context
|
| Resolution: |
→ fixed
|
| Status: |
reopened → closed
|
| Component: |
Core framework → Translations
|
| priority: |
normal → highest
|
| Severity: |
normal → critical
|
| Type: |
enhancement → task
|
| Version: |
→ 0.9
|
| Summary: |
[patch] Error handlers lack context → smart+question
|
| Type: |
task → defect
|
| Summary: |
smart+question → [patch] Error handlers lack context.
|
Where would
page_not_foundget theextra_content? I'm not sure this is possible...