Don't be scared, I checked in a whole bunch of tests too. ;-)
The problem we have is that CMF evaluates permissions for 'object'
and 'workflow' actions in the object context, and 'folder' actions in
the folder context. Other action categories are evaluated in the
context of the portal, which is rarely useful. Plone has 'document'
actions and we need permissions checked on the object, not the
portal. It is a one line change (with 4 tests). If you really don't
want it, we will have to resort to monkey patching ActionInfo.
http://plone.org/collector/3155
Stefan
On 16. Jul 2005, at 14:20, Jens Vagelpohl wrote:
On 16 Jul 2005, at 14:15, Stefan H. Holek wrote:
Update of /cvs-repository/Products/CMFCore
In directory cvs.zope.org:/tmp/cvs-serv12386/CMFCore
Modified Files:
Tag: CMF-1_5-branch
ActionInformation.py
Log Message:
CMFCore/ActionInformation.py: Permissions of action categories
starting
with 'document' are now evaluated in the object context instead of
the
portal context. This should probably be generalized some more.
Could you explain a bit more what problem this is solving? Check-
ins into the branch a day before a final production version is
released with insufficient problem descriptions that do not seem to
be critical bugfixes to CMF scare me. A lot.
jens
--
Software Engineering is Programming when you can't. --E. W. Dijkstra
_______________________________________________
Zope-CMF maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
