Chris Withers writes:
 > John Chandler wrote:
 > > 
 > > As already mentioned, not all errors (unfortunately) get handled by
 > > standard_error_message - authorisation being the main culprit. In addition, if
 > > an error occurs in a standard_error_message it'll also cause the plain, default
 > > error page to be displayed.
 > Hurm... I would have thought/it would be nice if an error occurs in
 > standard_error_message then, the next standard_error_message up the
 > acquisition path would get used, resorting to the hard coded one only if
 > there isn't anything else...
I do not agree with you here.

  You should be able to make "standard_error_message"s that
  do not generate secondary errors.
  If you fail, a crude minimal error handling should be okay
  as a last resort.


Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to