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:
The Experience Fragment Component will attempt to find a corresponding localized component in the following order.
- First it tries to find a language root.
- If not found, it tries to find a blueprint.
- If not found, it tries to find a live copy.
- 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)