Closed OwainJ closed 4 months ago
yep can reproduce.
oddly it all works if there is a property in the root, (it looks like if the second page is missing the tab definition then it doesnt work)
Fixed this today:
In v14 we must explicitly create the parent "tabs" in the content type when the parent is from a composition.
re-open . not quite fixed, works on first import, breaks on subsequent imports 😢
Fixed (again) - our tab cleanup was removing the tabs because they have not explict properties, they are now not removed if they are also inherited
Describe the bug I have two compositions which both include a
Content
tab, and a DocType which composes these that also adds it's own property to theContent
tab.After importing into Umbraco 14 RC4, using uSync v14 RC4, the DocType's property shows up in the
Generic
Tab, rather than the inheritedContent
tab.To Reproduce Steps to reproduce the behavior:
Content
tabContent
tabContent
tab or notExpected behavior The DocType's property should be in the
Content
tabScreenshots Left: v14 - Right: v13 This screenshot shows the property
Body Text
in theGeneric
tab on v14, whereas it was inside of theContent
tab on v13.About your Site (please complete the following information):
Additional context
herobannercomposition.config
```contentpage.config
```