-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 yuppie wrote:
yuppie wrote:
In Zope 2.10 'raise_standardErrorMessage', 'zpublisher_exception_hook' and therefore 'Publish.publish' did always (re-)raise errors after rendering. That made sure 'HTTPResponse.exception' was called and CookieCrumbler was able to hook into 'HTTPResponse._unauthorized'.
I'm now trying to figure out how this bug could be fixed: https://bugs.launchpad.net/zope-cmf/+bug/558340
For the record:
Meanwhile I figured out that there is a related launchpad issue https://bugs.launchpad.net/zope2/+bug/372632
Do you have a suggestion for resolving those two bugs?
and a workaround for the CookieCrumbler issue: http://dev.plone.org/collective/changeset/92340
Hmm, registering an exception view which re-raises the exception is definitely suggestive of something wrong in the plumbing.
I also removed some useless code in 'raise_standardErrorMessage': http://svn.zope.org/?rev=110801&view=rev http://svn.zope.org/?rev=110806&view=rev
Cool. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvEtewACgkQ+gerLs4ltQ7sCQCgwzq/lgYIRYIQq6AQ7oFyl5Yq qrAAnR2N+tVmAqleNsYiibUgTM/5mtwH =buo0 -----END PGP SIGNATURE-----