That's what I would think, but it doesn't seem to work. The header and footer work just fine, but not the standard_error_message. For example, I modified the root standard_error_message to contain the words "This is the root". Then created a folder called Testing, copied the same standard_error_message document into that folder and added the words "This was copied from..." in the beginning of the doc. I even restarted the server, just to be safe. When I still went to http://server/Testing/badfile, I got the error message from the root. That's why I figured, perhaps, when looking for the 'badfile', the namespaces were searched all the way down the tree. When it didn't find it anywhere, it just printed the error message from where it ended up, which was at the root. Makes sense to me.. Course I'm not sure how it all really works internally. -Ray ----- Original Message ----- From: "Christian Scholz" <cs@comlounge.net> To: "Ray" <zopelist@circle17.com> Sent: Monday, May 01, 2000 6:17 PM Subject: Re: [Zope] standard_error_message
Hi!
On Mon, May 01, 2000 at 05:49:24PM -0600, Ray wrote:
Quick question about error messages under Zope 2.1.0 under Linux:
Is it possible to overload the standard_error_message document, or do all errors essentially come from the root of the tree? I'd like to be able to create customized error messages for SiteAccess'd sites, or just different parts of the tree, for that matter.
As far as Aquisition is concerned you should be able to put another standard_error_message document in your folder which is then used (as it's the case with the header and footer as well).
-- christian