Quick question (hopefully!), is there any way to stop members from renaming the content nodes ie. I'm creating empty pages and applying role based protection on these pages. Site users then go into the back office and insert/amend the content for these pages.
When a member logs in the site programmatically loops through all of the roles that they have and displays/hides links based upon finding a matching item in the content tree. All is well until a user changes the name of an item in the content tree at which point the links will never appear because there is no match in the security roles. So my question is......it is possible to give users permission to create and name new content, to also allow them to amend this content (and existing content on the site) but stop them from ever renaming content?
What is the reason that users change the content name? Is it because it's being used in navigation etc.? If so I would recommend adding a textfield to contain the name in the menu and then instruct the editors to change that name instead.
Otherwise I suppose it's somehow possible to hook into an event when then document is being saved and cancel the change of the nodename. But it's not neccesarily a good user experience for the editors.
It's because all of the Member roles has to have an identically named piece of content. If an editor changes the name of the content then the match to the member roles no longer functions.
But i only want to stop them from renaming content and not from creating it.
Stopping users from renaming content
Hi folks,
Quick question (hopefully!), is there any way to stop members from renaming the content nodes ie. I'm creating empty pages and applying role based protection on these pages. Site users then go into the back office and insert/amend the content for these pages.
When a member logs in the site programmatically loops through all of the roles that they have and displays/hides links based upon finding a matching item in the content tree. All is well until a user changes the name of an item in the content tree at which point the links will never appear because there is no match in the security roles. So my question is......it is possible to give users permission to create and name new content, to also allow them to amend this content (and existing content on the site) but stop them from ever renaming content?
Thanks in advance,
Craig
Hi Craig
What is the reason that users change the content name? Is it because it's being used in navigation etc.? If so I would recommend adding a textfield to contain the name in the menu and then instruct the editors to change that name instead.
Otherwise I suppose it's somehow possible to hook into an event when then document is being saved and cancel the change of the nodename. But it's not neccesarily a good user experience for the editors.
Looking forward to hearing from you.
/Jan
Hi Jan,
It's because all of the Member roles has to have an identically named piece of content. If an editor changes the name of the content then the match to the member roles no longer functions.
But i only want to stop them from renaming content and not from creating it.
Any help would be great.
Craig
is working on a reply...