Wiadomość napisana w dniu 2009-08-28, o godz. 10:07, przez Tracy Reed: > I appear to have a bit of a heisenbug. When I have debug = True > everything works perfectly. When I have debug = False I get a 500 > error when accessing two views in particular. I'm not sure what makes > those views special or why the app would behave differently depending > on whether debug is True or False (aside from the obvious displaying > of templates vs debugging info such as tracebacks). When I get the 500 > Internal server error the following appears in the apache error_log: > > [Fri Aug 28 00:41:37 2009] [error] [client 216.105.40.112] > TemplateDoesNotExist: 500.html, referer: > http://mx1.mydomain.com/unsure > > Any ideas? I am using Django 1.1 on CentOS 5.3 with Apache 2.2.3 in > case it matters.
You do not have 500.html template and this error hides actual source of the error. See http://docs.djangoproject.com/en/dev/topics/http/views/#the-500-server-error-view . When DEBUG == True the 500 errors are processed by debugging view. -- Artificial intelligence stands no chance against natural stupidity Jarek Zgoda, R&D, Redefine jarek.zg...@redefine.pl --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
