#11990 closed (fixed)
TECHNICAL_404_TEMPLATE doesn't see URLConfs directly on request objects
| Reported by: | mattbennett | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | 404, urlconf, debug, template | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The default debug 404 template in django/views/debug.py assumes that the urlconf searched was the root urlconf. Since [4237] the urlconf can be set by middleware, so this is not necessarily the case.
The attached patch puts the module name of the urlconf being used into the template context, and modifies the template accordingly.
Attachments (1)
Change History (5)
by , 15 years ago
| Attachment: | technical_404_urlconf.patch added |
|---|
comment:1 by , 14 years ago
| milestone: | → 1.2 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 14 years ago
| milestone: | 1.2 → 1.3 |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
comment:3 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [14877]) Fixed #11990 -- Show the correct URLconf in the technical 404 template even if it was overridden, e.g. in a middleware. Thanks, mattbennett.