Allow to move content type out of inheritance from UI #15605
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Content types can use compositions or nested content types to inherit properties.
I guess there are pros and cons for both approaches.
However when migrating projects there are often nested content types.
We can changes parent id in database, but often I think it would we nice to handle this from UI is backoffice, which could change parent id and possible copy inherited properties.
In a migrated project I noticed the inheritance also may cause issues with ModelsBuilder models generation and if content type already is used as a content node. #15604
Beta Was this translation helpful? Give feedback.
All reactions