RE: [Zope] how to print error stack trace
-----Original Message----- From: Brian Hooper [mailto:brian@garage.co.jp] Sent: Thursday, September 09, 1999 11:05 To: Jay, Dylan Cc: 'zope@zope.org' Subject: Re: [Zope] how to print error stack trace
Just include
<dtml-var error_traceback>
in the body of the error mail (<!--#var error_traceback--> if you're using Zope 1).
Thanks alot. Also can anyone tell me why sometimes the standard_error_html is used and sometimes an error page is generated with stack trace but it didn't come from standard_error_html?
On Thu, 9 Sep 1999, Jay, Dylan wrote:
Just include
<dtml-var error_traceback>
in the body of the error mail (<!--#var error_traceback--> if you're using Zope 1).
Thanks alot. Also can anyone tell me why sometimes the standard_error_html is used and sometimes an error page is generated with stack trace but it didn't come from standard_error_html?
I think this is cuz errors can come from more than one place during the Zope request and it is not entirely consistent as you've noticed. I seem to recall some email from DC folk about this in particular a while back... I think the errors handled by ZPUblisher didn't call the standard error document for some reason... - kinda hazy answer from a kinda hazy jordan ------- Jordan B. Baker -- jbb@spyderlab.com weaving the web @ http://www.spyderlab.com
Errors which occur before the URL is fully resolved, and the resulting object called, generate hardwired error pages. Only after that process is complete is there an acquisition context in which standard_error_html can be found. I'm not sure if there's a better way to handle it. ----- Original Message ----- From: Jay, Dylan <djay@lucent.com>
Thanks alot. Also can anyone tell me why sometimes the standard_error_html is used and sometimes an error page is generated with stack trace but it didn't come from standard_error_html?
At 15:49 09/09/99 , Evan Simpson wrote:
Errors which occur before the URL is fully resolved, and the resulting object called, generate hardwired error pages. Only after that process is complete is there an acquisition context in which standard_error_html can be found.
I'm not sure if there's a better way to handle it.
Maybe use the context build up until the error occurs? /a/b/c/*BANG* use /a/b/c/standard_html_error /a/b/c/d/*BANG* use /a/b/c/d/standard_html_error.. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------
participants (4)
-
Evan Simpson -
Jay, Dylan -
Jordan B. Baker -
Martijn Pieters