Hi, I've experienced when there's an error in our templatecontext processing, so instead our 500.html our application using apache 500.html
perhaps you should check your log, to see there's an exception. -djibon- On Fri, Nov 6, 2009 at 4:05 PM, Maksymus007 <maksymus...@gmail.com> wrote: > > On Fri, Nov 6, 2009 at 9:34 PM, Brandon Taylor <btaylordes...@gmail.com> > wrote: >> >> Hi everyone, >> >> I'm doing my development on Ubuntu 9.1, Python 2.6.4, Apache2/mod_wsgi >> and Django 1.1.1. When setting DEBUG = False, and creating a view that >> I know will raise an exception, Apache's 500 error will show instead >> of the Django 500 view. >> >> I have created the 500.html template in my root templates directory >> I have set debug = False >> I have even set the "handler500" URL to point to my >> 'app.views.my_server_error_500' >> >> and the Apache error screen will still show up. >> >> Anyone have any idea why? >> > > not all exceptions are handled by django - for example syntax errors. > What kind of errors is yours? > > > > -- -------------------------------------------------------------- http://www.tumbletooth.org my linkedin profile : http://www.linkedin.com/in/bayuadji -------------------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
