You can use the Structure on the document type tab to decide what can and can't be created where.
You can't prevent what can be created under the 'Content' node, so to restrict it for uses you need to change their Start Node property in the Users section.
yes, i know about the structure, but wanted to extend that "logic" so I could limit what could be created under "content". And changing start node property is no good solution as then they loose the trashbin....
As the dialog is filtered by structure lower down in content, I thought there might be a way to achive this....
The only way I managed to do this, was to create a new content dll that inherits from the Umbraco one, and adds some code to remove all the create options from the menu. You have to update the apptree table in the db to use your one instead of the umbraco one. As its inheriting from the "proper" one, it should survive upgrades (unless the upgrade changes the database value back to the default content dll). Its a bit of a hack, but the root content node doesn't appear to be reachable by any of the events you'd normally use to access nodes in the tree through the API.
Filter create "page" dialog?
Anyone know how to filter the create "page" dialog in the content section? Would like to filter what document types a page can be at top level.
You can use the Structure on the document type tab to decide what can and can't be created where.
You can't prevent what can be created under the 'Content' node, so to restrict it for uses you need to change their Start Node property in the Users section.
yes, i know about the structure, but wanted to extend that "logic" so I could limit what could be created under "content". And changing start node property is no good solution as then they loose the trashbin....
As the dialog is filtered by structure lower down in content, I thought there might be a way to achive this....
The only way I managed to do this, was to create a new content dll that inherits from the Umbraco one, and adds some code to remove all the create options from the menu. You have to update the apptree table in the db to use your one instead of the umbraco one. As its inheriting from the "proper" one, it should survive upgrades (unless the upgrade changes the database value back to the default content dll). Its a bit of a hack, but the root content node doesn't appear to be reachable by any of the events you'd normally use to access nodes in the tree through the API.
is working on a reply...