Forget it Dieter!<br>Finally what I do is do the normal traverse (with the bobo_traverse) and I use another REQUEST variable (pathTraverse) to store the list expected at traverse_subpath and return the last object founded<br>
<br>I pretty sure (I don't test it for now) I can reconstruct TraversalRequestNameStack at __call__ level<br><br>Now I don't need the wrappers but the code goes fine<br><br>I didn't like so much the pathTraverse solution but works for me and that's the real important think
<br><br>Thanks and sorry!<br><br><div><span class="gmail_quote">2007/3/27, Dieter Maurer <<a href="mailto:dieter@handshake.de">dieter@handshake.de</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Garito wrote at 2007-3-27 02:50 +0200:<br>>How could be the __bobo_traverse__ to work as expected with out losting<br>>traverse_subpath?<br><br>You need to do strange things in "__bobo_traverse__" to loose the
<br>"traverse_subpath": in fact, you need to tamper with the<br>"TraversalRequestNameStack", or to no longer traverse to the objects<br>that set the "traverse_subpath" (in their "__before_publishing_traverse__"
<br>hook).<br><br><br>I fear you need to go back to the drawing board.<br><br>When I remember right, then your primary problem has been that<br>Zope's security machinery fails when "__bobo_traverse__" returns objects
<br>which are neither acquisition wrapped nor have their own security declarations<br>(such as strings, unicode, etc).<br><br>Therefore, I suggested that you instead of the elementary types return<br>wrappers for those types which behave identical to them but in
<br>addition have the security declaration "__roles__ = None" (which means<br>the object is public).<br><br>That seemed to work quite well for some time.<br><br><br>Now you are facing obscure problems (a user is not authenticated although
<br>you think it should be). Unless you are URL traversing to one of the<br>wrappers above (which you should not do of course), this problem<br>should have nothing to do with the wrappers.<br>Almost surely, it is a different problem -- which one, I cannot tell you.
<br>But, I gave some hints as to how I would proceed to understand the problem.<br><br><br><br>--<br>Dieter<br></blockquote></div><br><br clear="all"><br>-- <br>Mis Cosas<br><a href="http://blogs.sistes.net/Garito">http://blogs.sistes.net/Garito
</a>