Django custom error pages (404, 500)

11802 views

                  # Optional: custom error handlers
handler404 = 'myapp.views.custom_404'
handler500 = 'myapp.views.custom_500'


# In views.py
def custom_404(request, exception):
    return render(request, '404.html', status=404)


def custom_500(request):
    return render(request, '500.html', status=500)

                  {% extends "base.html" %}

{% block title %}Page Not Found{% endblock %}

{% block content %}
<div class="error-page">
  <h1>404 - Page Not Found</h1>
  <p>The page you're looking for doesn't exist.</p>
  <a href="{% url 'home' %}" class="btn">Go Home</a>
</div>
{% endblock %}

                  <!DOCTYPE html>
<html>
<head>
  <title>Server Error</title>
</head>
<body>
  <h1>500 - Server Error</h1>
  <p>Something went wrong. We're working on it!</p>
  <a href="/">Go Home</a>
</body>
</html>

Custom error pages improve user experience and brand consistency. I create templates named 404.html, 500.html, 403.html, and 400.html in the templates root. Django serves these automatically when DEBUG=False. For custom logic, I can override error handler views in urls.py. I ensure error pages don't depend on database or cache to prevent cascading failures. For 500 errors, I keep templates simple. I test error pages in production-like settings. This provides better UX than default Django error pages.

Priya Sharma

More from Priya Sharma

Django custom error pages (404, 500)

0 Comments

More from Priya Sharma