----- Original Message -----
From: "David VanKirk" <[EMAIL PROTECTED]>
To: "Jonathan" <[EMAIL PROTECTED]>
Cc: "Zope Mailing List" <zope@zope.org>
Sent: Friday, February 23, 2007 11:06 AM
Subject: Re: [Zope] Error Tracing in Zope 2.6
The error_log isn't helping. Apparently if your error is being caught
in a try block and uses an standard_error_page to show you the
exception and traceback it doesn't get logged in the error_log.
Is there anyway to maybe increase the traceback output from the
error_tb variable to traceback all the way to the DTML Method file?
I'll I get in traceback info is the traceback through the last few
*.py files, usually ending in the DTML_Try.py file since the page in
practically all enclosed in a try block. Very rarely does that
traceback prove useful unless the exception occurred in a PythonScript
that was called.
You never mentioned that you were trapping errors!
It is not a good idea to have 'practically all enclosed in a try block'
(especially if they are unqualified try stmts!)
I would remove the try stmts and see what is generating the errors.
Jonathan
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
