I'd like to collect some votes for a feature it's like to see added to Umbraco:
right now, if you nest document types (this is the only way to enforce site structure - allowing only certain types of pages below certain subsites), each level adds a new tab, making it:
* confusing for content editors
* hard to get the pages filled in correctly (validation for certain fields doesn't work, but the fields are required for the site to function - see my forumpost and tracker item about the Ultimatepicker)
* difficult to manage (if you have 4-5 levels of nested doctypes, to get an overview of all the properties that are available for it, you have to click your way up through all the doctypes and write them down ... )
Proposed solution:
* Make it possible to see parent document type's properties (inactive/greyed out) so you know what fields are available.
* allow me to add properties to existing tabs, not forcing new tabs to be created.
Allow nested doctypes to add properties to tabs belonging to the parent doctypes.
I'd like to collect some votes for a feature it's like to see added to Umbraco:
right now, if you nest document types (this is the only way to enforce site structure - allowing only certain types of pages below certain subsites), each level adds a new tab, making it:
* confusing for content editors
* hard to get the pages filled in correctly (validation for certain fields doesn't work, but the fields are required for the site to function - see my forumpost and tracker item about the Ultimatepicker)
* difficult to manage (if you have 4-5 levels of nested doctypes, to get an overview of all the properties that are available for it, you have to click your way up through all the doctypes and write them down ... )
Proposed solution:
* Make it possible to see parent document type's properties (inactive/greyed out) so you know what fields are available.
* allow me to add properties to existing tabs, not forcing new tabs to be created.
If you like this idea, please vote for this feature request here: http://umbraco.codeplex.com/workitem/28716
There's already a work item on Codeplex for this, http://umbraco.codeplex.com/workitem/21002
From what I've heard from some of the core team, this won't be happening in 4.x
Sorry i missed that one... duplicate ticket it is.
Looks like this has been fixed for 4.6 http://umbraco.codeplex.com/SourceControl/changeset/changes/4123655d60e2
is working on a reply...