Documentation

Resolving i18n issues due to missing path in JcrResourceBundleProvider configuration

Last update: Fri Jan 31 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

This article discusses the Adobe Experience Manager (AEM) issue where the Internationalization (i18n) functionality for UI strings is not working as expected, after upgrading from Service Pack 6.5.17 to 6.5.20. The resolution involves adding /etc to the included.paths property in the JcrResourceBundleProvider configuration.

Description description

Environment

Adobe Experience Manager (AEM) Version: 6.5.20

Affected Environment: Production (Author Instance)

Issue

After upgrading Adobe Experience Manager (AEM) from Service Pack 6.5.17 to 6.5.20, the Internationalization (i18n) functionality for UI strings was not working as expected in the production author environment.

Root cause

The missing /etc path in the org.apache.sling.i18n.impl.JcrResourceBundleProvider configuration prevented the system from accessing certain resource bundles or translations stored under that path.

Resolution resolution

To resolve the issue, follow these steps:

Access Configuration Manager

  1. Navigate to /system/console/configMgr in your AEM instance.

  2. Locate the org.apache.sling.i18n.impl.JcrResourceBundleProvider configuration.

  3. Update the JcrResourceBundleProvider configuration to add /etc to the included.paths property.

    Example configuration:

    code language-none 
    "included.paths": [
  "/libs",
  "/apps",
  "/etc"
  ]

Optional steps if the issue persists

  1. Restart the AEM instance to apply the configuration changes.
  2. Clear the AEM and dispatcher caches to ensure that the updated configuration is reflected.
  3. Test various components and pages to ensure that i18n keys are resolved as expected.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f