Forums / Setup & design / allow only specific subitems in container

allow only specific subitems in container

Author Message

Claudia Kosny

Thursday 15 June 2006 8:01:57 am

Hi there,

is there a way to specify which subitems can be created in a container?
Example: While the user should be able to create an folder directly under the root node, he should not have the possibility to create an folder within another folder. Or, another example, the user should be able to create products only in a specific folder identified by its node id, nowhere else.
I know that I can simulate something roughly similar on the user level using roles. Is there a way to do this on the object level, so that when I create a folder I can specify which type of objects can go in there?

I am using ezpublish 3.8.

Thanks

Claudia

André R.

Thursday 15 June 2006 9:20:48 am

The answer would be "Roles and policies".
And some examples would be:

content  	create  	Class( Artikkel, Gallery ) , ParentClass( Folder )
content 	create 		Class( Flash , Quicktime , Windows media , Real video , Image ) , ParentClass(  Gallery )
content  	create  	Node( Root ) , Class( Folder )

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Jeroen Sangers

Thursday 15 June 2006 9:40:16 am

Related to this: is there also a way to limit the number of classes shown in the dropdown list in the admin interface to only those classes that can be used?

André R.

Thursday 15 June 2006 9:58:35 am

Since you probably log in as an admin, you have full access to all functions and therefore all classes.

My previous answer was meant for the editor policy's, or other roles that you might create.
Tuning what they have access to, and what content they can place where and under what.

You can do the same thing for the admin role if you like to, but then you’ll have to remove the rule that states that admins have access to anything.
Witch means you’ll have to make changes to the admin role every time you add content classes, extensions or siteaccesses.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

liu spider

Thursday 15 June 2006 8:18:04 pm

play around with "Roles and polices" and read doc first

as mentioned, assign roles other than admin to those you want to restrict access

http://liucougar.scim-im.org
SCIM Input Method Platform
http://scim.sf.net
SJSD Online Editor
http://sf.net/projects/sjsd