Try tinkering with the standard_error_message document. It gets passed in the exception information so you can do an <!--#if--> to handle exceptions. --Paul

-----Original Message----- From: Brian Hooper [mailto:brian@garage.co.jp] Sent: Sunday, January 24, 1999 10:10 PM To: zope@zope.org Subject: [Zope] - catching DB errors

Hi -

I was wondering what is the recommended way to catch database errors before they get to where the user can see them - I am doing a lot of stuff using DTML scripting w/ SQLMethods, which works fine, but if possible I want to be able to shield the user from having to see 'Zope Unavailable' and/or a big traceback.

Is there any way to do this from DTML, or do I have to channel things through a try: except in an ExternalMethod?

Does anyone have a clever solution for this?

(By the way, I'm kind of interested in if the error messages can be collected and customized in one place - as I'm working in Japan, I want to change all of the server messages so they come out in Japanese. I expect there are probably other people that are interested in internationalization issues also - what have you all been doing?)

--Brian Hooper