A common question for AEM developers is, why are my i18n translations not showing up in my AEM environment? Recently, I have seen this problem coming up and I have the solution just for you.
During deployment, whether it is from AEM Author or Publish, when deploying new dictionary keys, it’s uncommon for new i18n configurations to not show up immediately after all the bundles have been installed and restarted. But when this happens, it’s because sometimes the Apache Sling I18N Supportorg.apache.sling.i18n is not registering the new dictionary keys that have been installed. In this article, I will provide a manual way for you to solve this problem.
2 ways to solve this problem
1. Restart the Apache Sling I18N Supportorg.apache.sling.i18n bundle
- Login to your AEM instance as admin
- Visit OSGI bundles console via http://localhost:4502/system/console/bundles
- Search for Apache Sling I18N Supportorg.apache.sling.i18n; you can use CTRL + F to find text on the browser
- Press on the stop button. This will stop the Apache Sling I18N Supportorg.apache.sling.i18n bundle; you should be able to see the status of the bundle set to “Resolved”
- Refresh the page
- Press on the play button. This will stop the Apache Sling I18N Supportorg.apache.sling.i18n bundle; you should be able to see the status of the bundle set to “Active”
- Head back to the page with the page with the i18n translations not working as expected, and you should see the dictionary value loaded as expected
2. Restart AEM
In this step, you can simple restart AEM, and the Apache Sling I18N Supportorg.apache.sling.i18n bundle should be active.
