Making the Language Copy Dropdown Languages List Configurable via Dialog | Community
Skip to main content
V
Adobe Employee
venkatdAdobe Employee
Adobe Employee
June 5, 2025
New

Making the Language Copy Dropdown Languages List Configurable via Dialog

  • June 5, 2025
  • 1 reply
  • 217 views
Request for Feature Enhancement (RFE) Summary:

Currently, the list of available languages displayed in the Language Copy dropdown is sourced from the out‑of‑the‑box definitions located in /libs/wcm/core/resources/languages. To add or customize languages (such as adding Kazakhstan using ISO code “kk” or “kk‑KZ”), customers must overlay this resource to /apps/wcm/core/resources/languages. This enhancement proposes introducing a configurable authoring dialog (or admin interface) that allows administrators to manage the languages list in the Language Copy feature without the need to overlay OOTB files.

Problem Statement:

  • Current Behavior:
    • The list of supported languages is static and defined in the repository under /libs/wcm/core/resources/languages.
    • Customizations require creating an overlay (/apps/wcm/core/resources/languages), which is manual, error‑prone, and requires technical expertise.
  • Impact:
    • Customers who need to add or update language definitions (for example, when a new language like Kazakhstan is needed) must rely on a technical workaround.
    • This process prevents non‑technical users (or content administrators) from easily managing the list and can lead to inconsistencies.

Proposed Solution:
Develop a new configuration dialog or admin interface that:

  • Provides a user-friendly interface for managing the list of locales available in the Language Copy dropdown.
  • Allows administrators to:
    • Add new language entries (e.g., defining the ISO code, display name, and any associated metadata).
    • Edit or remove existing entries.
    • Reorder the languages as needed.
  • Integrates seamlessly with the existing language copy functionality so that any changes in the dialog take immediate effect in the target dropdown.
  • Uses a persisted configuration, such as an OSGi configuration or JCR node under /apps, ensuring that changes remain consistent across updates and do not rely on repository overlays of OOTB files.

Benefits:

  • Improved Usability: Authors and administrators can manage language definitions in a straightforward, non‑technical manner without editing repository files.
  • Flexibility: The languages list becomes easily configurable, allowing for quick adaptations (e.g., new language support, corrections to existing definitions).
  • Reduced Maintenance Overhead: Eliminates the need to overlay and maintain duplicate resources, reducing the risk of misconfiguration after updates.
Use-case: A customer wants to include Kazakhstan in their language copy options. Instead of overlaying /libs/wcm/core/resources/languages to /apps/wcm/core/resources/languages and manually adding the language definition, the admin navigates to a “Language Copy Configurations” dialog, clicks “Add Language,” enters “Kazakhstan” with ISO code “kk” (or “kk‑KZ”), and saves the change. The Language Copy dropdown now immediately reflects the new language setting without any manual repository changes.
Current/Experienced Behavior: Currently the Language Copy dropdown is not configurable by the author
Improved/Expected Behavior:

Provides a user-friendly interface for managing the list of locales available in the Language Copy dropdown.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 all versions
Customer-name/Organization name: AGILENT TECHNOLOGIES - ACOM
Screenshot (if applicable):  
Code package (if applicable):  

    1 reply

    D
    DANIEL_ALFONZODE
    June 11, 2025

    This would be very useful. Some time ago, we opened a support ticket to inquire about the possibility of reducing ad-hoc language lists. We believe this should be an out-of-the-box feature available to admin users (not having such a wide list of languages if the site only uses a few).

    We developed an ad-hoc solution to modify this behaviour ourselves, but we were unable to make it functional for two reasons:

    - It was not “intelligent” enough to determine that if the translation already exists, it should not show the language.
    - When creating the “language copy”, clicking “open” did not take us to the created page but to the general root of the site pages, resulting in a loss of agility and leaving us in a similarly unproductive situation as having a wide list of languages.

    Having this possibility as an OOTB feature (allowing an administrator to easily select the number of languages available for creating translations) would be really helpful.

    Terms & ConditionsAccessibility statement

    Loading footer...