zope 2.7.0: no tracebacks produced
I am making a big upgrade and moving my products from 2.3.1 on HP-UX to 2.7.0 on windows 2000 and can't get zope to produce any tracebacks when it encounters errors. I've checked all the log files and monitor stdout to no avail. All I get is a brief html message with error type and value and instructions to check the error log. In the zope.conf file I have debug-mode on <eventlog> level ALL <logfile> path $INSTANCE/log/event.log level ALL </logfile> </eventlog> <logger trace> level ALL <logfile> path STDOUT </logfile> </logger> Any help here would be much appreciated!
According to Mika, David P (Research):
I am making a big upgrade and moving my products from 2.3.1 on HP-UX to 2.7.0 on windows 2000 and can't get zope to produce any tracebacks when it encounters errors. I've checked all the log files and monitor stdout to no avail. All I get is a brief html message with error type and value and instructions to check the error log.
from Zope-2.7.0/lib/python/ZPublisher/HTTPResponse.py: # Enable APPEND_TRACEBACKS to make Zope append tracebacks like it used to, # but a better solution is to make standard_error_message display error_tb. APPEND_TRACEBACKS = 0 \wlang{} -- Willi.Langenberger@wu-wien.ac.at Fax: +43/1/31336/9207 Zentrum fuer Informatikdienste, Wirtschaftsuniversitaet Wien, Austria
participants (2)
-
Mika, David P (Research) -
Willi Langenberger