Do not remove child nodes by Manage Publication of Experience Fragment(XF) | Community
Skip to main content
Adobe Employee
September 1, 2025
Investigating

Do not remove child nodes by Manage Publication of Experience Fragment(XF)

  • September 1, 2025
  • 2 replies
  • 504 views
Request for Feature Enhancement (RFE) Summary: Fix ManagePublication behavior to preserve child nodes in ExperienceFragment instead of deleting them
Use-case:
  • Use "Manage Publication" on particular parent folder on XF Structure.
BEFORE ManagePublication (Publish Environment):
/content/experience-fragments/customer/ └── en/ ├── company/ │ ├── company-overview-xf/ │ │ └── master/ │ ├── about-us-xf/ │ │ └── master/ │ └── contact-info-xf/ │ └── master/ ├── products/ │ ├── product-catalog-xf/ │ │ └── master/ │ ├── product-detail-xf/ │ │ └── master/ │ └── product-comparison-xf/ │ └── master/ └── ir/ ├── financial-report-xf/ │ └── master/ ├── investor-presentation-xf/ │ └── master/ └── earnings-release-xf/ └── master/
 
AFTER ManagePublication of /content/experience-fragments/customer/en (Publish Environment - ISSUE):
/content/experience-fragments/customer/ └── en/ └── [EMPTY - All child folders and XF content deleted from Publish]



Current/Experienced Behavior:
  • When using ManagePublication on ExperienceFragment folder (/content/experience-fragments/customer/en), all child folders (company, products, ir) and their XF content are completely removed from Publish environment.
  • All English XF content disappears from live site
  • Impact : Broken user experience, missing localized content, language-specific content loss (Some Japan customers faced incident due to this functionality.)
Improved/Expected Behavior:
  • Prevent deletion of child nodes in ExperienceFragment - this is a bug, not a feature request
Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud
Customer-name/Organization name: Manufacturing
Screenshot (if applicable):  
Code package (if applicable):  

               

2 replies

kautuk_sahni
Community Manager
Community Manager
September 5, 2025

@dmurata-1 Thanks for proposing this idea. This has been reported to the engineering under the internal reference SITES-34839. 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
dmurata-1Adobe EmployeeAuthor
Adobe Employee
September 8, 2025

@kautuk_sahni 

Thank you for your response and taking action on this issue.
I would like to emphasize that this problem has actually occurred in our customer’s production environment, which has led to a serious impact on business operations.
It would be greatly appreciated if this is taken into account when prioritizing the case.
I look forward to continued updates on the progress.