[Zope-CMF] standard_error_message must be DTML?!

[Lynn Walton]

Thanks for explaining, Dieter. I appreciate your help.  However, I checked and I actually did
have  just request   not here/request and having the standard_error_message in a skin still seems
to not be allowed for some reason. But, after further playing around, I found out that it was
related to
error_message, error_type, etc  not being found.  Tried here/error_message etc and didn't help.
As long as I put a "safety" in like:
tal:replace="error_message | default" it will work and deliver my custom zpt
standard_error_message rather than resorting to HTTPResponse's site error. So I'm now satisfied
that you CAN have a zpt standard_error_message. (I did read where there was a bug prior to Zope
2.4.1 that prevented this but it works with 2.4.1)

I've got an email into the zpt list to ask Evan how you access the error_message from there?
Lynn


Dieter Maurer wrote:

> Lynn Walton writes:
>  > I just tried to do the same thing ... make a page template with id standard_error_message
>  > like what Chris had, (using here/request  since that what Dieter thought might be involved.
> Sorry!
>
>   It might be that I did not look carefully enough at Chris' ZPT!
>
>   In ZPT, you would use either "request" or "here/REQUEST".
>
>   In the first case, you use the pre-defined ZPT variable "request",
>   in the second case, you acquire the request object from
>   the pre-fined variable "here".
>
>   Of course, the first is more natural and more efficient.
>
>   However, you must use "request" and "here/REQUEST" (not case!).
>   Using "REQUEST" or "here/request" will both cause
>   secondary errors reported by the build in "HTTPResponse" site error.
>
> Dieter