Simple question. Can I prevent the "create" content function to show all possible Document Types. I basically want to show only one Document Type (like WebsiteMaster) instead of a long list of all possible document types.
What you can definitely (and what I) do is to restrict authors to the homepage as a startnode, so from that point their "create" options are restricted based on what you set for each document type.
Would be interested to see if it's also possible from the content node, but haven't yet seen or heard of a way to do it.
When authors are restricted to a single website that is definitely the thing to do...
Problem here is that (some) authors do need access to multiple websites, which is possible by giving them access to top-level and then restricting the websites by unchecking "browse node" in the Permissions. Another pain here is that permissions are on user-level and not role based :-(((
So on root level some authors have already started to sabotage my project.. aargh. :-)
Guess my options are - event to prevent the creation of a new document on root-level unless the user is admin. - event on populating the list of document types (do not know if that is an existing event??)
First option would be a solution, cancel the new event on root level nodes (maybe it's even possible to roll your own loadContent class and override only the CreateRootNodeActions() method)
What I do Nico is create an extra node beneath the 'Content' node called something like 'Site Content'. All of your nodes will then be children of this node and you can then set permissions and restrictions as you normally would on a node. For your authors you can set them to start in the 'Site Content' node, and they'll never know that the top 'Content' node exists. Bit of a hack but it works for me.
Umbraco doesn't support real multisite. It cann't isolate each site absolutly. I have suggest that it should decide which document type/templates can be used by a user. then assign user to each site,this is flex way to create multisite. but no one reply.
@jonok, yeah, that would work. It's a bit ugly because of the extra level, but worth trying.
@sun, I think your suggestion is a totally different approach of how Umbraco handles document types right now. The allowed child nodes do not only depend on the root document, but also on the user. I like the concept, but it might involve a lot of changes in umbraco?
Create new node on Content level (top level)
Hi all,
Simple question. Can I prevent the "create" content function to show all possible Document Types. I basically want to show only one Document Type (like WebsiteMaster) instead of a long list of all possible document types.
Nico
Perhaps, but AFAIK.
What you can definitely (and what I) do is to restrict authors to the homepage as a startnode, so from that point their "create" options are restricted based on what you set for each document type.
Would be interested to see if it's also possible from the content node, but haven't yet seen or heard of a way to do it.
Dan
Thanx Dan,
When authors are restricted to a single website that is definitely the thing to do...
Problem here is that (some) authors do need access to multiple websites, which is possible by giving them access to top-level and then restricting the websites by unchecking "browse node" in the Permissions. Another pain here is that permissions are on user-level and not role based :-(((
So on root level some authors have already started to sabotage my project.. aargh. :-)
Guess my options are
- event to prevent the creation of a new document on root-level unless the user is admin.
- event on populating the list of document types (do not know if that is an existing event??)
Nico
First option would be a solution, cancel the new event on root level nodes (maybe it's even possible to roll your own loadContent class and override only the CreateRootNodeActions() method)
Second option is not possible afaik
Cheers,
/Dirk
What I do Nico is create an extra node beneath the 'Content' node called something like 'Site Content'. All of your nodes will then be children of this node and you can then set permissions and restrictions as you normally would on a node. For your authors you can set them to start in the 'Site Content' node, and they'll never know that the top 'Content' node exists. Bit of a hack but it works for me.
Umbraco doesn't support real multisite. It cann't isolate each site absolutly. I have suggest that it should decide which document type/templates can be used by a user. then assign user to each site,this is flex way to create multisite. but no one reply.
@jonok, yeah, that would work. It's a bit ugly because of the extra level, but worth trying.
@sun, I think your suggestion is a totally different approach of how Umbraco handles document types right now. The allowed child nodes do not only depend on the root document, but also on the user. I like the concept, but it might involve a lot of changes in umbraco?
Thanx for all replies
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.