Hi All,
Given that the source of bug #372632 appears to be code related to
allowing views on exceptions in Zope 2, I thought I'd try use this method.
I tried this, without much joy:
<browser:defaultView
for="exceptions.Exception"
name="error"
/>
<browser:page
for="exceptions.Exception"
template="html/error.html"
name="error"
permission="zope2.Public"
/>
So, how should I be wiring in views for exceptions?
Also, is there a base view class for exceptions anywhere that provides
the following or their equivalents?
kwargs = {'error_type': error_name,
'error_value': error_value,
'error_tb': error_tb,
'error_traceback': error_tb,
'error_message': error_message,
'error_log_url': error_log_url}
Finally, when a view is used to render and exception, is the userthe
current logged in user (as is the case with standard_error_message) or
Anonymous (as has annoyingly been the case with Unauthorized exceptions
in the past)
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
