Nested Components on Child Page Disappearing on Parent's Edit & Refresh - Inheritance/LiveCopy
I wanted to ask about the expectation of nested components with LiveCopy/Blueprint configurations:
I have a Blueprint (Parent) page that has a nested component structure like so:
------- Component 1 (Parent)
-------------- Component 2 (Child 1)
Then I have a Livecopy Child Page that inherits from Parent and initially looks the same:
Then on Child Page (Livecopy of Blueprint):
------- Component 1 (Parent)
-------------- Component 2 (Child 1)
------- Component 1 (Parent)
-------------- Component 2 (Child 1)
Then on the child page, I break inheritance of Component 2, delete it and copy from another page a 3rd Component to replace it, so it looks like this on the Child Page:
------- Component 1 (Parent)
------- Component 1 (Parent)
-------------- Placeholder Message for Child 2 that was Deleted
-------------- Component 3 (Child 2)
Now, I go back to the Parent page, and add a new component. However, if I return to the Child Page, and refresh the page - Component 3 is gone, but the new component is added. Now my page structures looks like this:
Parent page:
------- Component 1 (Parent)
-------------- Component 2 (Child 1 within Parent)
------- Component 4
Parent page:
------- Component 1 (Parent)
-------------- Component 2 (Child 1 within Parent)
------- Component 4
Child Page:
------- Component 1 (Parent)
------- Component 1 (Parent)
-------------- Placeholder Message for Child 1 that was Deleted
------- Component 4I'm wondering what the proper authoring experience should be. Is it suggested that the Parent Component (Component 1) should have inheritance broken on the Child Page before adding new child components? Or is there a specific way to configure our Blueprint/Livecopy to have this functionality?