I just realized that I accidentally named the template 400.html not 404.html... d'oh. I definitely need a better way of diagnosing 500 errors.
Thanks to the pointer to the email settings. I will set that up, but I'm wondering if there's a way to direct django to log those errors rather than email it. I see there is a middleware component, django-db- log that seems to do that. I am using django-logging, and it would be very handy to find a way to get the error messages to go the log file instead. That aside, I couldn't imagine a live production deployment of django using email for logging errors. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
