I think the problem is that any changes made to standard_error_message don't appear to have any effect. I've tried just simply changing the text, add ' - wibble' after 'Zope Error' and the old error message is still displayed, even after restarting Zope...
This is what happens when an exception is raised while rendering standard_error_message (obtained through acquisition).
ZPublisher renders the default standard_error_message, rather than let a problem go unreported.
Yup, just discovered this myself. :-) I put a buggy dtml expression in the document and Zope displays a default message rather than the custom one I've generated - removing the buggy stuff brings the custom version. Thanks to Martin for pointing me to the 404 handling on zope.org, I've solved the initial problem I was having with getting changes recognised in the standard_error_message in Zope's root, and now have it mailing a basic error report to the webmaster. There are a few issues Chris noticed when he was doing some stuff, but I'm going to take a look at these further before posting more on the subject. Cheers, 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.