Create a ghost component if a component is moved to another container in a livecopy | Community
Skip to main content
P
PeterLeugner
March 26, 2025
Investigating

Create a ghost component if a component is moved to another container in a livecopy

  • March 26, 2025
  • 1 reply
  • 233 views
Zusammenfassung der Funktionsverbesserungsanfrage (RFE):

When a component is moved from a container to another container in a livecopy the component appears again after sync. There should be a ghost component to prevent this.
Anwendungsfall:

If you move a component from one container to another in a livecopy, the component appears again in the original container after syncing with the blueprint.
Steps to reproduce:
- Create a new page with the template Content Page and open it
- Add a Layout Container to the page
- Add a component to the layout container (for instance a Text Component) and fill in some text.
- Create a LiveCopy of the above page with Standard Rollout Config and open the LiveCopy
- Add a second Layout Container to the LiveCopy
- Drag (move) the component in the first container to the second
- In the page settings synchronize with the blueprint
- The component appears again in the first container

There should be a ghost component in the first container when the component is moved, but none is created.
Aktuelles/erlebtes Verhalten: The component appears again after sync
Verbessertes/erwartetes Verhalten: A ghost component should be created in the original container to prevent the reappearing of the component
Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben): 6.5.22
Name des Kunden/der Organisation: Atruvia
Screenshot (sofern zutreffend):  
Code-Paket (sofern zutreffend):  

1 reply

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
March 27, 2025

@peterleugner 

Thanks for proposing this idea.
This has been reported to the engineering under the internal reference SITES-30311. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.
Kautuk Sahni
Terms & ConditionsAccessibility statement

Loading footer...