to do that click the user under 'User permissions', below 'Select pages to modify their permissions' navigate to the node you're setting up, and uncheck Delete. Click save, and that's it!
That's odd, I've just tried that because I need exactly the same functionality for something I'm working on now. This is how it is for me: I have a node with stores. Each store manager will get a user. For that user I've selected for 'Start Node in Content' the corresponding store node, so when he logges in only that node is visible under Content. Then I did what I said above and it works, the user can create child nodes under his node, and delete them. Maybe you had 'Replace child node permssions' checked?
Are the children a different document type? Are the children you want the user to delete already created? In my case the children aren't there, the user creates/edits/delets them.
In my case in the default permissions of the 'editor' user type I have unchecked delete. I thought it's worth mentioning. Unfortunately I cannot offer real help on this issue as I don't know how these permissions work in the guts of umbraco.
Question regarding permissions
I'm using 4.0.4.2 for the first time, and I think I might not be understanding the permissions on content nodes properly.
I am trying to set up a node where the editor role cannot delete the node itself, but can delete and children of that node.
How should I go about this?
Thanks in advance.
Hi Andrew,
to do that click the user under 'User permissions', below 'Select pages to modify their permissions' navigate to the node you're setting up, and uncheck Delete. Click save, and that's it!
Unfortunately, when I do that, new child pages created lack the delete permission.
Is there any way to set permissions for an node's future children to be different to the permissions on the node itself?
That's odd, I've just tried that because I need exactly the same functionality for something I'm working on now. This is how it is for me: I have a node with stores. Each store manager will get a user. For that user I've selected for 'Start Node in Content' the corresponding store node, so when he logges in only that node is visible under Content. Then I did what I said above and it works, the user can create child nodes under his node, and delete them. Maybe you had 'Replace child node permssions' checked?
I didn't, I made sure of it - and when I do have that checked, it just goes into an endless progress bar and nothing happens.
So, essentially, it looks like something's a little wrong with my instance of Umbraco, then?
Did you try to check it with something like firebug? Maybe behind that endless progress bar there are some useful answers to what the problem may be.
In the finest tradition of weird IT issues, it's now no longer going into infinite progress. It's workign fine.
However, the delete permission set on the parent is still apllied to all new children, which is not what I'm after.
Are the children a different document type? Are the children you want the user to delete already created? In my case the children aren't there, the user creates/edits/delets them.
They are adifferent document type, yes. There are a couple already there, and the rest will be created when data entry proper starts.
They are not directly beneath the content root for the editor - they're three levels down, in fact.
At the moment, I'm fearing all I'll be able to do is to stress to the site's editor how careful they have to be not to delete the wrong thing.
In my case in the default permissions of the 'editor' user type I have unchecked delete. I thought it's worth mentioning. Unfortunately I cannot offer real help on this issue as I don't know how these permissions work in the guts of umbraco.
is working on a reply...