U4-4791 - Allow changing Master Document Type hierarchy

Created by Douglas Robar 30 Apr 2014, 13:19:56 Updated by Shannon Deminick 26 Jun 2017, 05:38:46

I would LOVE to have the ability to change an existing document type's master inheritance/hierarchy.

For example, if I create a document type and later realize I should have set it as using the 'SEO' document type as a Master I would want to alter the document type hierarchy/inheritance by being able to set/change/remove the 'Master' of an existing document type.

Currently this can't be done. If you forget to set the Master when you first create a document type that's that, you can't add it later on. Similarly, you can't change the Master setting from one document type to another. Nor can you remove a master document type setting (for instance, not all doctypes require an SEO master).

All you can do currently is delete the errant doctype and make it again... which is unacceptable if you've already got a bunch of content tied to that doctype because as soon as you delete the doctype all the content will go away with it. Granted, you could take the very time consuming approach of changing the existing doctype's name/alias, create a new and proper doctype with the original name/alias, and then use the 'Change Document Type' functionality on every single(!) content page and then delete the original doctype.

I can imagine a UI similar to that of the current 'Change Document Type' feature, giving options to map existing data in content pages to equivalent properties on the new master. Also, a way to handle the situation in which the new master doctype has an alias collision with a property on the existing document type.

Comments

Douglas Robar 30 Apr 2014, 13:24:19

@abutland I don't suppose you'd be interested in taking this on? @sebastiaan mentioned to me at #umbBEfest that the core has the functionality and "just" needs a UI. Given your excellent work on the "Change Document Type" feature this might be right up your alley! <>


Shannon Deminick 26 Jun 2017, 05:38:47

Closing issue due to inactivity - see blog post for details https://umbraco.com/blog/issue-tracker-cleanup/


Priority: Normal

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions:

Due in version:

Sprint:

Story Points:

Cycle: