[Zope-PTK] Some coming attractions+issues

[Jeffrey P Shell]

I have been working rather steadfastly over the last couple of days on a
Permissions Cleanup, at least in PTKBase.  Part of this effort involves the
creation of a CMFBasePermissions module which defines all of the permissions
used in PTKBase.  One benefit of this is that we don't get duplicitous
permissions ("Add portal content" versus "Add Portal content") on minor
spelling\capitalization differences.  Another is that this module becomes a
nice reference point for answering the question "What permission should I
use here?".

The big change that's coming, however, is the extensive use of Declarative
Security, a new Zope 2.3 feature.  However, there is a small bug in Zope
2.3.0's SecurityInfo.py class (in lib/python/AccessControl/SecurityInfo.py)
that is fixed in the 2.3.1 release, the Zope CVS Trunk, and the Zope 2.3 CVS
branch.  If you don't have one of these fixed versions, the patch is as
follows::  (This will also be posted on cmf.zope.org later today).

The checkins won't be happening until sometime after noon, EST.

Index: SecurityInfo.py
===================================================================
RCS file: /cvs-repository/Zope2/lib/python/AccessControl/SecurityInfo.py,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- SecurityInfo.py     2001/01/16 20:01:09     1.7
+++ SecurityInfo.py     2001/02/08 16:45:35     1.8
@@ -242,7 +242,7 @@
         for permission_name, names in permissions:
             roles = getRoles(permission_name, ())
             if len(roles):
-                entry = (permission_name, tuple(names), tuple(roles))
+                entry = (permission_name, tuple(names),
tuple(roles.keys()))
             else:
                 entry = (permission_name, tuple(names))
             __ac_permissions__.append(entry)



Jeffrey P Shell, jeffrey@Digicool.com
http://www.digicool.com/ | http://www.zope.org