2👍
The following is required in settings
module in order to display diagnostic page after errors:
DEBUG
is True- The client (web browser) is connected from localhost or from any IP address listed in
INTERNAL_IPS
. - The variable
TEMPLATE_CONTEXT_PROCESSORS
contains"django.core.context_processors.debug"
or is left on the default value.
You can distinguish the web server’s error 500 page from Django’s error page easy by different text like this:
“… There’s been an error. It’s been reported…” (This is from the default template.)
if you do import handler500 from django.conf.urls
(or django.conf.urls.defaults in old Django) in the main urlconf.
2👍
You could have an error in your middleware in process_request before you can get to the error page. Although, that you could access some pages would suggest that this is not the problem.
- [Django]-Reading RSS feed and displaying it in Django Template | feedparser
- [Django]-Django rest framework – Field level validation in serializer
- [Django]-Is it possible to disable a field in Django admin?
- [Django]-Django: Making a value in a model unique specific to a user
- [Django]-Django only submitting csrf token in forms?
- [Django]-What's the best way to map the main urls in a django project?
- [Django]-Finding overlapping dates in a specific range in Django
- [Django]-Class attribute inheritance in Django models
- [Django]-Kubernetes liveness probe fails when the logs show a 200 response
Source:stackexchange.com