Florent Guillaume wrote:
Does it work to just set __parent__ to the container? Or does the zopesecuritypolicy require more accurate context?

I think that might work, though I've had previous problems with actually being allowed to *set* the __parent__ to the container. :)

I would also be worried about code that checks whether an object has a previous parent and sends a different event (move). Given that, it's easier to just removeSecurityProxy on the code..


Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to