Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Contexthub Issues on AEM 6.4 (Style System and i18n)

Avatar

Level 1

Hi Experts,

We are using Contexthub on AEM 6.4. Found that when authoring a targeted component for each segment, the style that was selected from the style system is not carried over to the segment-specific version - it only shows on "default". The style system option is also not there when in "Targeting" mode so there is no way to set the style for each segment. Aside from this, the i18n can only be seen on the "default" segment/experiences. For other segments, it always shows the English labels.

 

Has anybody encountered this behavior? Any help, insights, or suggestions are all welcome. Thanks in advance.

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hello,

It is not possible to use the style system in the targeting mode. An alternate way to achieve that can be by creating the Experience Fragments [1] with different style options and then target using those Experience Fragments.
Regards,
Vishu

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

Hello,

It is not possible to use the style system in the targeting mode. An alternate way to achieve that can be by creating the Experience Fragments [1] with different style options and then target using those Experience Fragments.
Regards,
Vishu

Avatar

Level 1

Hi @Vish_dhaliwal,

 

Thanks! I tried this approach with the style system and got the selected styles to carry over to the other segments. Would this mean then, that for every segment, a separate experience fragment would have to be created, even if it is just a style difference?

 

I also tried this approach to see if it solves the i18n issue wherein, when authoring for segments, the component seemingly disregards the current page language and keeps using the EN translations. Is this a limitation of the Personalization feature of AEM?  Is there a way to work around this? 

 

Much thanks!

 

Regards,

Nadeen