Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM Translator to Manage Dictionaries replicate change

Avatar

Avatar
Validate 1
Level 1
daf99
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
daf99
Level 1

Likes

0 likes

Total Posts

9 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
daf99
Level 1

14-07-2020

Hello everyone,

I have implemented in my AEM project the Translator to Manage Dictionaries.

I was thinking that i should able to edit a label and then replicate that change for all the others AEM instances, but i don't any option to do it in the Translator interface. Then i found the note that is in the image below.

daf99_0-1594724280514.png

This note means that if have several AEM instances and i want to update some label without make a deploy, i have to make the same update in each one of the AEM instances manually?
There is no option to replicate the update as it's possible to be done with content?

Thank you.

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct Reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct Reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
vanegi
Employee

14-07-2020

Hi @daf99 ,

To add to this, we have an OOTB implementation that AEM provides to manage dictionaries. A console for managing the various translations of texts used in component UI. This console is available at http://<hostname>:<port-number>/libs/cq/i18n/translator.html. See https://docs.adobe.com/content/help/en/experience-manager-64/developing/components/internationalizat... for more details.

 

With respect to the given use case, the i18 keys can be replicated to publisher in different ways as mentioned below.

·         Manually creating the i18 nodes in publisher

·         Creating the package from author and deploying it to publisher

·         Replicating the nodes through tree activation

Login to treeactivation.html - http://<<Host>>:<<Port>>/etc/replication/treeactivation.html

 

 

Thanks,

Vaishali

Answers (1)

Answers (1)

Avatar

Avatar
Establish
MVP
Nupur_Jain
MVP

Likes

165 likes

Total Posts

186 posts

Correct Reply

76 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Establish
MVP
Nupur_Jain
MVP

Likes

165 likes

Total Posts

186 posts

Correct Reply

76 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 25
View profile
Nupur_Jain
MVP

14-07-2020

Hi @daf99 

 

The note you specified basically means that the translation dictionary should be part of source code. As a best practice, we keep the translation in code base and they are installed as part of deployment. As mentioned in note, this process makes tracking of changes easy and maintainable.

 

The translation dictionary interface is mostly used when we need to make changes that are urgent and needed  prior to deployment.

 

Also, the translation dictionary can be replicated using tree activation feature and should work properly. You can also read https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-i18n-nodes-activate-on...

 

Hope it helps!

Thanks,

Nupur