Dynamic template experience fragment localization is not working

[julkarna]

Hi everyone, 

I have created a React SPA project with archetype 45, created a dynamic template from SPA Page template and used experience fragment for page header so that I can leverage experience fragment localization feature for multiple language. The issue is if I create pages using both template (SPA Page, Custom Content Page) experience fragment localization is not working as expected. The fragment path I am using for both templates - 

Experience fragment and content tree - 

  

Now my expectation is when I create a page under fr/fr node the created page should have localized header. The localization works only if all the page created with same template, if I create a page with SPA Page template and another with Custom Content Page template the header fragment localization does not work properly. 

 

/content/test-spa/fr/fr/home is created with SPA Page template - 

/content/test-spa/fr/fr/home-with-custom created with Custom Content Page

Now if I create another page using SPA Page template, the fragment localization now works for pages created from SPA Page but pages created with Custom Content Page does not render the localized experience fragment. It seems the localization works only for the last used template type pages. 

Why the localization is not working for both template type pages? How can I resolve this?

[arunpatidar]

Hi @julkarna 
Please make sure you are using core experience component not the foundation one in your custom template.

Please compare the xf type in default and custom template.

Localisation supported only with core XF template

https://experienceleague.adobe.com/en/docs/experience-manager-core-components/using/wcm-components/e... 

[julkarna]

Hi @arunpatidar ,

Both templates are using the "test-spa/components/experiencefragment" component. Which is - 

[kautuk_sahni]

@EstebanBustamante @Tethich @SureshDhulipudi @martin_ecx_io @Saravanan_Dharmaraj @BrianKasingli @pradeepdubey82 @abhishekanand_ @Anil_Chennapragada @daniel-strmecki would you please take a moment to review this question? We would be grateful if you could share your suggestion on this question.

[pradeepdubey82]

Content hierarchy and XF hierarchy should match with supported locale in AEM, you should not have 'french' node, it should be two character 'fr' similarly for all other supported locales.