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
Solved! Go to Solution.
Views
Replies
Total Likes
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/introdu...
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
Hi @arunpatidar ,
it can't be cache because the issue is already visible on author.
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/introdu...
@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!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies