I think this is a bug. Would you be willing to file a Collector issue at collector.zope.org about this? - C On Fri, 2003-01-17 at 00:37, Operaciones - Piensa Technologies wrote:
Thanks Dieter:
Now goes the 2nd part of this story: I got rid of all code in the standard_error_message, I just left the minimum HTML tags to print out some text.
It happens that the error is still there.... (the 'Also, an error occurred while attempting...bla bla..' error)
Another interesting thing: If I "view" (hit the VIEW management tab) while on the standard_error_message editing form, it happens that it renders and dislays correctly, that is it doesn't generate that secondary exception. I am not passing values or parameters to the standard_error_message.
I forgot to mention that this same application rendered the standard_error_message perfectly fine while running in Zope 2.5.1, it only happens in 2.6.0 so, something must have changed.
Again, any light or comments on this beheavior of Zope is more than welcome.
Edward
On Thu, 2003-01-16 at 14:53, Dieter Maurer wrote:
When processing a Zope request produces an exception, Zope searches "standard_error_message" and renders it.
If this rendering produces another (secondary) exception, Zope uses a trivial build in error handler and reports
Also, an error occurred while attempting to render the standard error message.
Your "standard_error_message" contains a bug.
Add "dtml-try ... dtml-except" to it and make an output in the "except" part.
Dieter
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev ) -- Chris McDonough <chrism@zope.com> Zope Corporation