On Jan 15, 9:34 am, Shev <[EMAIL PROTECTED]> wrote: > Thanks for the feedback - I'm not seeing any traceback - just the > vanilla "Internal Server Error" page that apache2 comes with, > seemingly for all exceptions (e.g. failed import, bad template > operation, bad logic in a view, etc. etc.) When I turn DEBUG = True > on in the settings, then the standard Django traceback/error page > comes on just fine - but I don't want that to show on the production > server, of course. >
Then you need to check the apache error log, the traceback should be included there. > Is it possible that the 500.html is not being found yet the 404.html > is being found? Both files are in the same place and have the same > ownership/permissions, and the 404.html *is* working. > Seems unlikely, but without a traceback its hard to be sure. Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
