This spun off from #3519352: Content templates, part 3b: store exposed slot subtrees on individual entities. In that issue, we're changing ComponentTreeItem to store multiple subtrees as individual field items, each tied to a specific slot that is exposed by the full view mode's content template. If the template changes such that a slot no longer exists, or is no longer exposed, entities' ComponentTreeItem values will have stale data.
Whenever a ComponentTreeItem is saved, it should be automatically purged of any items that are targeted at slots in the template which are no longer exposed.
None.
Comments
Comment #2
wim leersWith #3468272: Store the ComponentTreeStructure field property one row per component instance, that would become a lot simpler to achieve.
Comment #3
lauriiiJust seeing this now. I believe this requires some consideration regarding how users would move exposed slots from one place to another within a template. The fact that slots were getting purged later enabled users to achieve this without a specific UI affordance.
In the meanwhile, we could think through how we'd implement this with publish workflow. If you delete a slot, that change should only take place during publish, not when the slot gets deleted from the template.