Opened 17 years ago

Closed 17 years ago

#6269 closed (duplicate)

Enhancement request: Replace ViewDoesNotExist stacktrace with custom error page

Reported by: eibaan Owned by: nobody
Component: Core (Other) Version: dev
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


If you misspell a view name, you get a black-on-white stacktrace that doesn't look as clean and nice as the usual technical_500_response view. It would be great if that raw stacktrace would be replaced by a "django style" error page. My observation was, that, when doing demos with a development snapshot and the development server, people accept the django error page but start to get nervous if they see that raw stack trace. Strange, but true and probably easy to change.

I don't know whether there's a reason to not include request middleware processing and URL resolving in the try-except block in django.core.handlers.base.BaseHandler.get_response(). I've attached a patch to include them.

Attachments (1)

bettererrorpage.diff (1.3 KB ) - added by eibaan <eibaan ät googlemail> 17 years ago.

Download all attachments as: .zip

Change History (2)

by eibaan <eibaan ät googlemail>, 17 years ago

Attachment: bettererrorpage.diff added

comment:1 by Karen Tracey <kmtracey@…>, 17 years ago

Resolution: duplicate
Status: newclosed

I think this is also covered by the patch in #6094. If you could confirm by trying out that patch it would be helpful.

Note: See TracTickets for help on using tickets.
Back to Top