Dave Fregon wrote:
On Tue, 2007-09-04 at 15:27 -0500, Héctor Velarde wrote:
MattBowen told me on IRC that workflow scripts cannot be proxied and
that's why I am having this problem at test time.
That's true, but there is a simple way around it.
Try using an unproxied script that calls the main script in your skins
folder, that _is_ proxied .. works for me.
i usually route around the entire issue by a) using external methods as
workflow scripts and b) having the workflow scripts do nothing other than
delegate to a real python function or method that lives in an appropriate
place in my product code.
that being said, your original problem may not be related to the security
settings on the script at all. it may be that even if you get the security
all dialed in, there's some explicit security check in the code that is
causing the problem. if you end up performing your operation from trusted
code but still have the problem, then you'll need to dig more deeply to find
out exactly why the action is being disallowed. see
http://plone.org/documentation/how-to/debug-unauthorized.
-r
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
