Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
SOLVED

i18n issue

Avatar

Level 3

In my author 

/libs/ cq/i18n/dict.en_us.json. The keys are correct

But in publisher same path if I check  the keys values are different 

How we can make  both should be in sync?

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @user96222 ,

First you should not make changes directly in libs i18n folder, create a overlay of it in your apps folder.
Then once it is created in author , you can replicate it directly from node in crx.


Thanks
Tarun

View solution in original post

3 Replies

Avatar

Correct answer by
Community Advisor

Hi @user96222 ,

First you should not make changes directly in libs i18n folder, create a overlay of it in your apps folder.
Then once it is created in author , you can replicate it directly from node in crx.


Thanks
Tarun

Avatar

Community Advisor

Hi @user96222 

  1. Go to the AEM Web Console on the author instance (http://localhost:4502/system/console/configMgr) and search for the "Apache Sling Replication Agent - Default Agent" configuration.

  2. Edit the configuration and add the following properties:

    • Name: cq-i18n-dict
    • Type: content
    • Paths: /libs/cq/i18n/dict
    • Enabled: true
  3. Save the configuration and go to the AEM Web Console on the publisher instance (http://localhost:4503/system/console/configMgr).

  4. Search for the "Apache Sling Replication Agent - Default Agent" configuration on the publisher instance.

  5. Edit the configuration and add the following properties:

    • Name: cq-i18n-dict
    • Type: content
    • Paths: /libs/cq/i18n/dict
    • Enabled: true
  6. Save the configuration and wait for the replication to complete. You can check the replication status in the Replication Status console (http://localhost:4503/etc/replication.html). 



Avatar

Community Advisor

@user96222 

 

I second @TarunKumar . Any edits to /libs is strictly prohibited.

  1. It could have a more widespread impact on the system
  2. Your changes can easily be overwritten by a Service Pack
  3. In AEMaaCS, you won't even be allowed to deploy under /libs 

 

Prefer creating the i18n dictionaries specific to your project, like https://github.com/adobe/aem-guides-wknd/tree/main/ui.apps/src/main/content/jcr_root/apps/wknd/i18n 

  • If you are using AEMaaCS, only way to deploy i18n is via code
  • If you are on AEM 6.5, you can either of the following approaches:
    • Deploy on author/publish via code 
    • Create on author and replicate via CRXDE
    • Deploy the i18n via package on author and publish

Aanchal Sikka