Expand my Community achievements bar.

Localized Reference for Experience Fragment


Community Advisor


Request for Feature Enhancement (RFE) Summary: Localized Reference for Experience Fragment

We are using AEM 6.4.8/6.5.8 and using experience fragments component in our page templates for header and footer implementations similar to WKND sites.

In template, we add experience fragment component with "/content/experience-fragments/us/header" as fragment path and when we create pages in /content/<project>/us/page, we are able to see the US Header.


Now we created language copy of the experience fragment to "/content/experience-fragments/fr/header", and now created page under "/content/<project>/fr/page", due to Localization implementations in experience fragment core component, automatically FR header is picked up on the FR page.

Current/Experienced Behavior:

Now US Team, changed something in US header and planned to publish sometime next week.

parallelly FR team changed some page content and when trying to publish FR page, it is showing US Header as outdated as part of References publish.. which is weird.

Improved/Expected Behavior: the localization implementations done in core component experience-fragments model (com.adobe.cq.wcm.core.components.internal.models.v1.ExperienceFragmentImpl" also to be done for "com.adobe.cq.xf.impl.ExperienceFragmentsReferenceProvider" so check only for localized references.
Environment Details (AEM version/service pack, any other specifics if applicable):



Customer-name/Organization name:  
Screenshot (if applicable):  
Code package (if applicable):  
1 Comment




@Shashi_Mulugu This request has been raised to the product team via the Jira CQ-4325061. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

Status changed to: Investigating