A simple addition for the urls.py that exposes the 404/500 templates during development. This way you can test how those look. They're mounted under /404/ and /505/ respectively.
Add this at the bottom of your main urls.py.
1 2 3 4 5 6 7 | # serve media in development mode and expose the 400/500 docs for testing
if settings.DEVELOPMENT_MODE:
urlpatterns += patterns('',
url(r"%s(?P<path>.*)$" % settings.MEDIA_URL[1:], 'django.views.static.serve', {'document_root': settings.MEDIA_ROOT}),
url(r'^500/$', 'django.views.generic.simple.direct_to_template', {'template': '500.html'}),
url(r'^404/$', 'django.views.generic.simple.direct_to_template', {'template': '404.html'}),
)
|
More like this
- Template tag - list punctuation for a list of items by shapiromatron 9 months ago
- JSONRequestMiddleware adds a .json() method to your HttpRequests by cdcarter 9 months, 1 week ago
- Serializer factory with Django Rest Framework by julio 1 year, 4 months ago
- Image compression before saving the new model / work with JPG, PNG by Schleidens 1 year, 4 months ago
- Help text hyperlinks by sa2812 1 year, 5 months ago
Comments
This doesn't really work for the 500 template. In testing with this urlconf, your 500 template will be rendered with context from all your context processors. In a real 500 error, Django does not make that context available and your 500 template could look very different (if, say, you depend on media_url to get media).
And generating a real 404 is never very hard to do.
#
Please login first before commenting.