Experience Fragment | localizedFragmentVariationPath | for non-standard region/language sites | Community
Skip to main content
P
pradeepmoolemane
New Participant
September 8, 2022
Solved

Experience Fragment | localizedFragmentVariationPath | for non-standard region/language sites

  • September 8, 2022
  • 1 reply
  • 874 views

Hello team,

We have site structure in AEM like "/content/project-site/eu/en" where as EU is europe region and EN -english site. Similarly corresponding XF structure -  Experience Fragment structure "/content/experience-fragments/project-site/eu/en/site"

 

and for German site "/content/project-site/eu/de" and XF - "/content/experience-fragments/project-site/eu/de/site".

We are using AEM SPA with reactJs to render the pages. 

 

Issue is model.json always have XF localizedFragmentVariants - "/content/experience-fragments/project-site/eu/en/site" for EU/DE site.

 

Expected localized fragment variants path for site "/content/project-site/eu/de" must be "/content/experience-fragments/project-site/eu/de/site".

 

Please let me know how we can achieve this retrieving language specific XF for EU/DE site.

We have achieved this for multipage sites but not finding way to customize for SPA pages where data exported via model.json.

 

Quick responses much appreciated. thanks

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

Hello, resolved the issue by extending the abstract class "AbstractComponentImpl" and implementing "ExperienceFragment" interface.

 

and we need to override the methods "getLocalizedFragmentVariationPath()" and getChildren() methods.

1 reply

P
pradeepmoolemaneAuthorAccepted solution
New Participant
September 14, 2022

Hello, resolved the issue by extending the abstract class "AbstractComponentImpl" and implementing "ExperienceFragment" interface.

 

and we need to override the methods "getLocalizedFragmentVariationPath()" and getChildren() methods.

Terms & ConditionsAccessibility statement

Loading footer...