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
- A custom 500 handler which is AJAX-aware by mallipeddi 4 years ago
- Decorator for enabling views only when developing by damd 1 year, 6 months ago
- Keep settings.py in version control safely by mboersma 4 years, 11 months ago
- Use MEDIA_URL in 500 error page by bthomas 3 years, 2 months ago
- base class to easily expose json based web services by jpablo 1 year, 6 months ago
Feed of latest snippets
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.
#