Hello Christian,
Thanks, tried that. The problem is when new users arrive, they get
ModifyContent permission in the site root. Now I shall add a
subscriber for the new_user event or denying ModifyContent from
Authenticated users should be enough? I am still a bit puzzled.
Thursday, August 23,
Hi,
On Thu, 2007-08-23 at 08:31 +0200, Adam Groszer wrote:
Hello Christian,
Thanks, tried that. The problem is when new users arrive, they get
ModifyContent permission in the site root. Now I shall add a
subscriber for the new_user event or denying ModifyContent from
Authenticated users
Hi,
I ended up in overriding the permission storage map. This might not be
so conservative, but seems to work. Kills any not ALLOWED permission
and stops propagation.
ALLOWED = ['zope.View', 'zope.app.dublincore.view', ...]
class trashPermManager(AnnotationPrincipalPermissionManager):
def
Hello,
Is there a sane way to stop permission propagation to sublocations?
Let's say I have a site, and somewhere below there is a folder as a
trashcan, unneeded objects get moved to here. Users must not modify
objects in the trash. Users usually will get ModifyContent permission
at the site
Am Mittwoch, den 22.08.2007, 21:00 +0200 schrieb Adam Groszer:
Hello,
Is there a sane way to stop permission propagation to sublocations?
Let's say I have a site, and somewhere below there is a folder as a
trashcan, unneeded objects get moved to here. Users must not modify
objects in the
