standard_error_message woes!
Gaaah! I'm totally miffed/pissed/confused/sad about this. I have Zope 2.2.4, and if I go to: http://docwhat.gerf.org:9673/fish (an non-existant object) I get the HTTPResponse.py _error_html() function as called by notFoundError(). Now, if I go to: http://zope.org/fish I get a nice fully customized error page, which includes where I *might* have ment to go.... What's going on! According to http://www.zope.org/Members/JohnC/StandardErrorMessage I should be able to get this to work, he has a <dtml-if "error_type=='NotFound'">... example even! Gaaaaaaaahhhhhhhhhhhhh!!!!!!! *goes off in a corner, pulling out hair while quitely sobbing* -- "This is the Steve Allen show. To those of you lunging for the channel selector, 'Good Night!'" The Doctor What: Un-Humble http://docwhat.gerf.org/ docwhat@gerf.org KF6VNC
Just catching up on my mail...
Gaaah! I'm totally miffed/pissed/confused/sad about this.
I have Zope 2.2.4, and if I go to: http://docwhat.gerf.org:9673/fish (an non-existant object) I get the HTTPResponse.py _error_html() function as called by notFoundError().
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. Looks like you're handling a 404 (Not Found) so I'd advise checking your custom page is correct first as an error there could be causing the custom error message to be superceded. All good fun :-/ Hope that's a useful starter... John -- John Chandler / Software Developer / New Information Paradigms Ltd [ Linux in the office, AmigaOS in the home, PalmOS in the pocket ] ------------------------------------------------------------------------ The opinions above aren't those of my company... ...but then, they aren't really mine either.
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... Is that the case? cheers, Chris
participants (3)
-
Chris Withers -
John Chandler -
The Doctor What