We have moved to GitHub Issues
Created by Mads Rasmussen 14 Jul 2015, 09:08:54 Updated by Claus Jensen 16 Dec 2015, 11:34:49
Subtask of: U4-112
Right know all available composite content types is part of the content type model. To clean up the model we could move availableCompositeContentTypes to it’s own service and follow the pattern from available templates and available content types (child nodes).
PR is here: https://github.com/umbraco/Umbraco-CMS/pull/951
Along with moving the availableCompositeContentTypes from the model to a separate service, this PR also does:
Seems good to me - I've tested that creating document types with composition (on creating) works. Also tested adding in properties on the doctype itself - on a tab inherited from composition, then deleting the composition - everything seems to work as intended.
Backwards Compatible: True
Affected versions: 7.4.0
Due in version: 7.4.0
Sprint: Sprint 5