#15607: Custom error templates in a single Django application
-----------------------------------------+----------------------
Reporter: jose | Owner: nobody
Status: closed | Milestone:
Component: HTTP handling | Version: 1.2
Resolution: needsinfo | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
-----------------------------------------+----------------------
Comment (by russellm):
@jose -- Look very closely at my example. I deliberately mounted 2
included URLs at the same base -- /foo. Lets say I browse to /foo/bar. It
doesn't match anything in app1.urls or app2.urls. Do we display the
app1.handler404 or the app2.handler404? Both app1.urls and app2.urls match
the /foo prefix -- how do we disambiguate between the two?
I agree with Adrian -- I'm not convinced that this can be done in a non-
crufty way. There might be room to do this sort of thing if we rework the
way URLs are defined, but given the current structure, I'm not sure it can
be done cleanly and unambiguously.
--
Ticket URL: <http://code.djangoproject.com/ticket/15607#comment:6>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
