On 11 October 2010 18:54, Streamweaver <streamwea...@gmail.com> wrote:
> I'm still looking into this if anyone has any insight.
>
> On Oct 7, 2:04 pm, Streamweaver <streamwea...@gmail.com> wrote:
>> On our 500 error page I would like to display a message specifically
>> if the error is in the Database connection, and not display the
>> message on any other uncaught exception but I can't seem to figure out
>> a way to catch the specific exception going to a 500 page.
>>
>> Has anyone done this?

You can process the exception using a middleware[1], so that you can
later access it's type in your custom 500 handler[2].


[1]: 
http://docs.djangoproject.com/en/dev/topics/http/middleware/#process-exception
[2]: 
http://docs.djangoproject.com/en/dev/topics/http/views/#the-500-server-error-view

-- 
Łukasz Rekucki

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-us...@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.

Reply via email to