On 3/4/10 11:40 PM, Laurent Mignon wrote: > I've the same kind of issue in my application. The 'workaround' used > is to specifically mark the request during traversal request and play > with security iin the update method only if the request is not marked > as used into the traversal conext: Thanks, but in my case the problem is not simply that security checks are happening that I want to bypass in widget traversal. My problem is that I need to know the current user in order to determine what data is being edited by the form.
David -- David Glick Web Developer Groundwire 206.286.1235x32 [email protected] http://groundwire.org ONE/Northwest is now Groundwire! _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
