Forums / Setup & design / Restrict create privilege where owner of parent is self.

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Restrict create privilege where owner of parent is self.

Previous topic

Setup & design

Next topic

Author	Message
Nathan Sharp	Friday 29 September 2006 10:42:22 am I've looked around a little and haven't found this yet, so my apologies if it has already been requested. I am soon to be administering an image gallery site for a group of people. I would like each person to have create/edit/remove permissions for their own gallery. Obviously I could manually create top-level folders and roles for each person that do this, but I was hoping for something a little simpler. If I could restrict the create privilege to only allow people to create new nodes if the parent node is already owned by them, I think I could implement this with a static list of roles and a user group. 1) Allow users to create folders directly in a top-level node, but not in the subtree 2) Allow users to create folders, galleries, images in any sub-tree of the top-level <i>where they own the parent</i>. 3) Allow users to edit/remove any of the above that they own. Is this reasonable? Is there some way to accomplish it that I haven't thought of? Regards, Nathan P.S. In a matter of a few hours I was able to put together a site for this group that seriously wowed them. Thanks!
Kristof Coomans	Saturday 30 September 2006 6:05:31 am Hi Nathan There was a ParentOwner patch (by Gabriel Ambuehl) submitted for eZ 3.8 on the sdk-public mailinglist (http://lists.ez.no/pipermail/sdk-public/2006-March/002046.html). It didn't make it's way into it but it's definitely worth a try. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Nathan Sharp	Monday 02 October 2006 6:00:55 am That looks right on! Thanks!

Author

Message

Nathan Sharp

Friday 29 September 2006 10:42:22 am

I've looked around a little and haven't found this yet, so my apologies if it has already been requested. I am soon to be administering an image gallery site for a group of people. I would like each person to have create/edit/remove permissions for their own gallery. Obviously I could manually create top-level folders and roles for each person that do this, but I was hoping for something a little simpler. If I could restrict the create privilege to only allow people to create new nodes if the parent node is already owned by them, I think I could implement this with a static list of roles and a user group.

1) Allow users to create folders directly in a top-level node, but not in the subtree
2) Allow users to create folders, galleries, images in any sub-tree of the top-level <i>where they own the parent</i>.
3) Allow users to edit/remove any of the above that they own.

Is this reasonable? Is there some way to accomplish it that I haven't thought of?

Regards,
Nathan

P.S. In a matter of a few hours I was able to put together a site for this group that seriously wowed them. Thanks!

Kristof Coomans

Saturday 30 September 2006 6:05:31 am

Hi Nathan

There was a ParentOwner patch (by Gabriel Ambuehl) submitted for eZ 3.8 on the sdk-public mailinglist (http://lists.ez.no/pipermail/sdk-public/2006-March/002046.html). It didn't make it's way into it but it's definitely worth a try.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Nathan Sharp

Monday 02 October 2006 6:00:55 am

That looks right on! Thanks!