Experience Fragments Smart Translations Structure (BROKEN) | Community
Skip to main content
Level 6
March 14, 2024
Question

Experience Fragments Smart Translations Structure (BROKEN)

  • March 14, 2024
  • 1 reply
  • 390 views

For experience fragments, dealing with the template structure, header and footer, it works as expected. When the experience-fragment lives inside of the editable template structure, the localization all works.

Adobe documentation suggests:

Fallback

The Experience Fragment Component will attempt to find a corresponding localized component in the following order.

  1. First it tries to find a language root.
  2. If not found, it tries to find a blueprint.
  3. If not found, it tries to find a live copy.
  4. If not found, it defaults to the experience fragment configured in the component.
 
But now, as a content author, I will create a new page in the language masters.  I drag and drop the experience fragment on a page. When I live copy that page to sub pages, the experience-fragment's link is stuck, and does not get reflected. 
 
Why does editable templates > structured experience fragments work as expected, but when content authors are authoring the experience fragment at the language-master level, and when the page is rolled out, the paths don't update. Od enough, only the en language master, the locales are rolled out as expected. 
 
 

 

/content +-- experience-fragments \-- wknd +-- language-masters +-- en +-- customXF (language master) \-- es +-- customXF (language copy from /content/experience-fragments/wknd/language-masters/en) +-- us +-- en +-- customXF (live copied) \-- es +-- customXF (live copied) \-- ch +-- de +-- customXF (live copied) +-- fr +-- customXF (live copied) \-- it +-- customXF (live copied) +-- wknd +-- language-masters +-- en +-- customPage (language master) \-- es +-- customPage (launage copied from /content/wknd/language-masters/en) \-- fr +-- customPage (launage copied from /content/wknd/language-masters/en) \-- it +-- customPage (launage copied from /content/wknd/language-masters/en) +-- us +-- en +-- customPage (live copied) \-- es +-- customPage (live copied) +-- ch +-- de +-- customPage (live copied) +-- fr +-- customPage (live copied) \-- it +-- customPage (live copied)

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

aanchal-sikka
Community Advisor
Community Advisor
March 15, 2024

@supportmember 

 

Can you please try by using "Creating a Translation Integration Configuration"

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/sites/administering/reusing-content/translation/integration-framework#creating-a-translation-integration-configuration

 

The link rewrites here work with Content Fragments, I am hoping the same for Experience Fragments as well

Aanchal Sikka