Experience Fragment and countries | Community
Skip to main content
S
SarahBo2
Level 2
July 26, 2024
Solved

Experience Fragment and countries

  • July 26, 2024
  • 2 replies
  • 1028 views

Hi there,

In our project we have experience fragments header/footer set by default in templates. We recently added a new country (Greece) to our site. Greece is not able to retrieve the experience fragment in each page. In some pages it take the Greece one, in others the default one.

The site path is : /content/project/gr/gr

The experience fragment path is : /content/experience-fragments/project/gr/gr/site/header/master

 

As for now sometimes it takes the default fragment that is /content/experience-fragments/project/de/de/site/header/master.

 

We're having this issue just with this country. Other countries correctly recover the referenced xf.

 

Does anyone have a solution for this issue?

Me and my team thank you in advance.

Sarah

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 arunpatidar

Hi @arunpatidar ,

It seems that the problem could be the name of the language : gr. Because if we set the language in "el" and we create the xf under el, all pages automatically recover the correct xf. Is it possible that adobe supports just any specific country/language? Could it be a relationship between the language and the xf?

Below the updated paths:

 

path site--> /content/project/gr/el

path experience --> /content/experience-fragments/project/gr/el/site/header/master

Thank you for your help

 


Hi @sarahbo2 
You can check this, I think for Greece the language code is el

https://github.com/michaelwittig/node-i18n-iso-countries/issues/57

https://www.w3.org/International/O-charset-lang.html 

 

You can check AEM language root config - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/sites/administering/introduction/tc-prep

2 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
July 26, 2024

Hi @sarahbo2 

It might be a cache issue. Please try bypassing the cache and check again.
Additionally, review the scenario where the default Experience Fragment might be appearing:

Experience Manager Core Components: Experience Fragment Fallback

Arun Patidar
    S
    SarahBo2Author
    Level 2
    July 26, 2024

    Hi @arunpatidar , 

    it can't be cache because the issue is already visible on author.

      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      July 26, 2024

      Hi @sarahbo2 
      Can you also check, for which page type the default XF is appearing, could be issue with template configuration.

      Arun Patidar
        kautuk_sahni
        Community Manager
        kautuk_sahniCommunity Manager
        Community Manager
        August 1, 2024

        @sarahbo2 Did you find the suggestions from users helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

        Kautuk Sahni
        Terms & ConditionsAccessibility statement

        Loading footer...