Paul Everitt wrote:
> On Dec 9, 2008, at 10:15 AM, Hanno Schlichting wrote:
>> Tom Gross wrote:
>>> is there any repoze-component for catching zope2-exceptions except
>>> cgitb which is unsuitable for production environments. omitting cgitb
>>> results in a white page which isn't too good eighter. is there a
>>> which can return customized error pages?
>> If you find anything, please let us know. For Plone we need this
>> functionality as well, so we can still offer nicely formatted "not
>> found" and general "error" pages.
> For Plone, do you need the "nicely formatted" to include links to CSS
> that are automagically assembled by the WSGI app (Plone)? If so, you
> have a bit of a chicken-or-egg situation.
Right. I think we don't need integrated error pages having exactly the
same design as the backend application. What people care about is
something that looks better than just a plain error. If it is a static
page with minimal CSS that is fine with me. Serving error pages from a
Zope / Plone backend is a bad idea in terms of speed anyways.
> If Plone's future includes repoze.squeeze, which might have already
> written a generated set of static stuff to disk for serving by a
> StaticURLParser or some such, then I retract my point.
I think the approach repoze.squeeze takes is how the future of our
ResourceRegistries should look like. If someone wants to own the task of
replacing RR with repoze.squeeze for real inside Plone, I think we are
very welcome to the idea.
Repoze-dev mailing list