Move inherited content types #14559
bjarnef
started this conversation in
Features and ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In old days of Umbraco inherited content types were the approach, when one wanted to share (inherit) properties between content types. However as the solution was growing it could also become a mess as parent properties was inherited in the structure, so at some point it often ended up we properties on content nodes, which wasn't relevant to the specific page.
I don't recall if it was possible to move the child content types, but it seems it isn't at the moment.
I think inherited document types has its benefits, but it structure in backoffice, but also that one is guaranteed the parent properties are inherited to child content types, where with composition one have to ensure to select to composition content type on each other content type, which need to "inherit" the composition properties. Besides that a composition can't be used in another composition, where a content type can inherit several levels of ancestor content types.
However from backoffice UI it isn't possible to move the nested content types although it is possible to change parent ID in the database. I think it would be useful to be able to move the nested content type and ideally copy the parent/ancestor properties depending on which level the content type is moved to.
But if moving under a different structure there is change for property aliases may collide with each other.
As a start I think it would be great at least to move to root level or within a folder/container to "break" the connection with the inheritance and would save some time re-creating the content type and may not break any content already created.
Beta Was this translation helpful? Give feedback.
All reactions