I wanted to throw 2 cents in to this thread from my previous
problems/questions about error_message.
I think they are slightly related.
Maybe someone can filter my newbie-isms and use some of this in the Dogbowl.
I would like to have more control over the standard_error_message
auto-rendering of error_message and error_tb. These should be treated more
like "typical" methods in Zope to be consistent with everything else. (like
> What is error_message?
> Where does the autoformatting come from, and how do I alter it?
> Can I modify it to just grab the error and not all the other Zope stuff?
> Why is this so stealthy compared to the rest of Zope?
> Why should I have to "turn off" debugging for tracebacks to be commented
> in the HTML? With my Zope understanding so far...if it is an object, then
I can include it or not in my
> standard_error_message. So why is it hardcoded in Zope?
> Example: If I have error_tb in my standard_error_message, then it renders,
> not - it's hidden. Current Zope renders it anyway.
> Why isn't it treated like an object like the rest of Zope?
> Is there a library of these error messages that can be modified to provide
> better information for users to find what they are looking for. They come
> from somewhere?
> Formulator allows you to customize your error messages. It would be great
if Zope_Error handling were that >friendly.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
> Of Noel Duffy
> Sent: Thursday, October 18, 2001 10:20 AM
> To: Steve Alexander
> Cc: seb bacon; [EMAIL PROTECTED]
> Subject: Re: [Zope-dev] standard_error_message and displaying non-html
> Steve Alexander writes:
> > seb bacon wrote:
> > > I don't believe there is a clean way. I've changed the source not to
> > > display its own html at all. It's not nice, but I suppose that's the
> > > benefit of OSS.
> > Is there a FishBowl proposal on remedying this? If not, there
> should be one.
> > Perhaps someone who has this itch to scratch can get the ball rolling?
> First, thanks for the quick response.
> Secondly, I would be willing to start this process, but my
> knowledge of Zope internals is patchy at best, so I might not
> be the best person for this. Still, if no-one else wants to,
> I will give it a go.
> Just to clarify, I am only concerned at present with the code in
> HTTPResponse that, in the case of an exception, scans for
> <!doctype html or <html, and wraps them in html if these are
> not found. (Seb, does this cover the problems you experienced?)
> I think there is a more general problem of making Zope
> "content-neutral", but that is a proposal for another time.
> Noel Duffy.
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -