optilude optil...@gmail.com added the comment:
The pastie is gone, but the problem is basically this: z2bob does the
``browserDefault()`` lookup in ``next_name()`` and is capable of providing a
name to
continue traversal to. However, the ``browserDefault()`` protocol returns a
tuple
optilude optil...@gmail.com added the comment:
Here is a pretty rough patch for this (not very well tested, and there possibly
a
security issue with this)
Index: repoze/zope2/z2bob.py
=
==
--- repoze/zope2/z2bob.py
optilude optil...@gmail.com added the comment:
Here's a better, safer patch:
Index: repoze/zope2/z2bob.py
=
==
--- repoze/zope2/z2bob.py (revision 11017)
+++ repoze/zope2/z2bob.py (working copy)
@@ -313,6 +313,10
New submission from optilude optil...@gmail.com:
repoze.zope2 predates the inclusion of ZPublisher.pubevents in Zope 2, so it
does
not notify the relevant events.
The following patch attempts to add them, though some are a bit hard to place
since they relate to transactions. Sorry, no tests
optilude optil...@gmail.com added the comment:
Yes, I figured, but since I was digging into this and found a solution, I
wanted to at
least record it somewhere.
See also https://mail.zope.org/pipermail/zope-dev/2012-January/043930.html
__
Repoze Bugs b
