Documentation

Fixing content fragment access issues in Adobe Experience Manager

Last update: Fri May 09 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

This article addresses an issue where content fragments in Adobe Experience Manager as a Cloud Service - Sites are inaccessible across development, staging, and production environments due to incorrect repository configurations and externalizer settings. The solution involves verifying and updating the externalizer configuration to ensure proper routing and seamless access to content fragments.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) - Sites

Issue/Symptoms

When you open the Content Fragment and it fails to load, you will find that the repoURL is incorrect.

Resolution resolution

To resolve this issue, follow these steps:

  1. Verify the externalizer settings in the codebase under Open Services Gateway Initiative (OSGI) configurations such as config.author. Locate the file com.day.cq.commons.impl.ExternalizerImpl.xml.

  2. Ensure the externalizer configuration includes entries for each environment. For example:

    code language-none 
    author $[ env:AEM_EXTERNALIZER_AUTHOR;default=http://localhost:4502]     publish $[ env:AEM_EXTERNALIZER_PUBLISH;default=http://localhost:4503]     preview $[ env:AEM_EXTERNALIZER_PREVIEW;default=http://localhost:4503]

    Modify or add entries as necessary based on the environment setup.

  3. Deploy the changes and verify that content fragments are accessible without redirection issues.

  4. Confirm that accessing content fragments now points to the correct repository and ensure consistent functionality across all environments.

Default Behavior of the Externalizer in AEM as a Cloud Service

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f