Creating content directly under 'Content' node allows user to use any document type
Hi
i don't how to prevent this but, when the user creates new content and selects the top level 'Content' node, the 'choose document type' dropdown presents all the defined document types. for example i have a document type 'faqitem' and faqitem is an allowed child type of only the faq document type because i it needs to inherit properties of its parent. Anyone know how i can prevent this?
Thanks for your reply. I wanted to do that however i need a way for my client to manage the navigation himself because the logical navigation of the site doesn't follow the physical structure of the content (which is common in the majority of website).
It just seems that this, i.e. restricting document types from being on the top level, was 'missed'.
Basically, this tells Umbraco to go use the top level as the "home page". I think that would then allow you to restrict your user to the site top level node and have your navigation generate correctly.
I stand corrected. Nik i think its doing something a bit more than that. I'm using an asp.net theme with this site and setting that value to false causes the theme to not display.
That may be an issue with the Theme's CSS path. Check the html head section of your site, you may find the references to the css files are returning 404 errors.
Yes, toggeling this to false will change the meaning of your your relative paths. So, you may want to try to use an absolute path to your assets "/" without domain.
Creating content directly under 'Content' node allows user to use any document type
Hi
i don't how to prevent this but, when the user creates new content and selects the top level 'Content' node, the 'choose document type' dropdown presents all the defined document types. for example i have a document type 'faqitem' and faqitem is an allowed child type of only the faq document type because i it needs to inherit properties of its parent. Anyone know how i can prevent this?
thanks
Sean
Hi Sean,
I don't know of anyway to prevent this. It's best practise to create a parent node and put all you pages under that;
Content
- Website
--Home
-- News
Your 'Website' doctype would then restrict on what types of children it can have.
This approach also makes navigational xslt easier to write.
Chris
Hi Chris
Thanks for your reply. I wanted to do that however i need a way for my client to manage the navigation himself because the logical navigation of the site doesn't follow the physical structure of the content (which is common in the majority of website).
It just seems that this, i.e. restricting document types from being on the top level, was 'missed'.
Hi Chris, you should be able to control this by modifying the following setting in the web.config:
Basically, this tells Umbraco to go use the top level as the "home page". I think that would then allow you to restrict your user to the site top level node and have your navigation generate correctly.
Hope that helps.
-- Nik
Sorry, meant to address this to Sean.
Thanks Nik i'll give that try.
its set to true, i've changed it to false - has no apparent effect. :(
I stand corrected. Nik i think its doing something a bit more than that. I'm using an asp.net theme with this site and setting that value to false causes the theme to not display.
Hi Sean,
That may be an issue with the Theme's CSS path. Check the html head section of your site, you may find the references to the css files are returning 404 errors.
Chris
Yes, toggeling this to false will change the meaning of your your relative paths. So, you may want to try to use an absolute path to your assets "/" without domain.
Hopefully this helps to some extent.
-- Nik
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.