Is there any plan to have all the errors use the standard_error_message? Many of our clients want custom Unauthorized errors, for which we have to use a dtml-raise tag or modify the ZPublisher sources. Neither is ideal. The same applies to 'Resource not found' errors, except the only way to do it is to modify the source. I hate having to modify the zope source to do things, it makes upgrading a real pain (still have a couple sites running 1.10.2 because we don't have time to patch 1.10.3). I've actually got a bit of time coming up that I have earmarked for moving our stuff up to Zope2. I'd like to eliminate the need of modifying the source code as much as possible. So if noone else is working on this problem, I can do it. While on the topic of patching Zope, we have a few other patches floating around here. There's one which allows for all passwords to be encrypted (both normal and UserDB pwds) and one that adds BCC to the Mail Host. Plus a patch to mod_auth_mysql it get it to understand zope formatted roles (so you can use a mysql DB for both zope/non-zope site authentication). Anybody interested in these? --- John Eikenberry [jae@kavi.com - http://zhar.net/] ______________________________________________________________ "A society that will trade a little liberty for a little order will deserve neither and lose both." --B. Franklin
Just noticed that it looks like the Not Found error has been changed to use standard_error_message in Zope 2.1.0. As is implied in this collector entry: http://classic.zope.org:8080/Collector/796/view It doesn't say whether it works for Unauthorized though. Though from a quick test on the Zope site (which I understand is using the latest CVS version...), I would guess not. Just wanted to head off the obvious pointers to this new feature. ;) On Thu, 4 Nov 1999, John Eikenberry wrote:
Is there any plan to have all the errors use the standard_error_message?
Many of our clients want custom Unauthorized errors, for which we have to use a dtml-raise tag or modify the ZPublisher sources. Neither is ideal. The same applies to 'Resource not found' errors, except the only way to do it is to modify the source.
I hate having to modify the zope source to do things, it makes upgrading a real pain (still have a couple sites running 1.10.2 because we don't have time to patch 1.10.3).
I've actually got a bit of time coming up that I have earmarked for moving our stuff up to Zope2. I'd like to eliminate the need of modifying the source code as much as possible. So if noone else is working on this problem, I can do it.
While on the topic of patching Zope, we have a few other patches floating around here. There's one which allows for all passwords to be encrypted (both normal and UserDB pwds) and one that adds BCC to the Mail Host. Plus a patch to mod_auth_mysql it get it to understand zope formatted roles (so you can use a mysql DB for both zope/non-zope site authentication).
Anybody interested in these?
---
John Eikenberry [jae@kavi.com - http://zhar.net/] ______________________________________________________________ "A society that will trade a little liberty for a little order will deserve neither and lose both." --B. Franklin
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope No cross posts or HTML encoding! (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
--- John Eikenberry [jae@kavi.com - http://zhar.net/] ______________________________________________________________ "A society that will trade a little liberty for a little order will deserve neither and lose both." --B. Franklin
participants (1)
-
John Eikenberry