On Jan 14, 2008 11:36 PM, Shev <[EMAIL PROTECTED]> wrote: > > Hi all - I'm using apache2 and mod_python (sitting behind nginx) and > the latest trunk version of django, and have setup the 500.html error > template as suggested. Unfortunately, it doesn't seem to work - > whenever there's a problem causing django to throw an exception, I end > up seeing the simple and ugly default apache "Internal Server Error" > page instead of my custom 500.html error page. > > My custom 404.html page works just fine, so I'm puzzled why its > 500.html cousin isn't working. Also, though I've setup the ADMINS > param in the settings file, I never get any emails when exceptions are > thrown (though I guess if the 500.html isn't being used, that should > be expected). > > Any ideas? Thanks in advance for any help! >
What traceback do you see exactly? I can think of two possibilities -- either your 500.html is not being found, or you are running into something where Django is not catching the exception (see for example http://code.djangoproject.com/ticket/6094 for cases where Django does not yet trap exceptions). The exact traceback would hopefully point to one or the other of these. 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 -~----------~----~----~----~------~----~------~--~---
