DocumentationExperience Cloud KCS

Rich Text Editor not loading in Content Fragment Editor Adobe Experience Manager

Last update: September 9, 2026

In Adobe Experience Manager (AEM), the Rich Text Editor (RTE) might not appear or initialize in the Content Fragment Editor, preventing editing in rich text mode. This issue can result from configuration problems, missing dependencies, browser-related issues, or access restrictions. To fix this issue, review editor dependencies, validate AEM configurations, and verify browser and access settings.

Description description

Environment

Adobe Experience Manager (AEM)

Issue/Symptoms

  • When using the Content Fragment Editor in Adobe Experience Manager, the Rich Text Editor (RTE) does not appear or initialize.
  • Editing in rich text mode is unavailable.

Cause

Misconfigurations, missing client libraries, browser compatibility issues, or access restrictions.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Review recent changes or deployments in your AEM environment that impact the Content Fragment Editor or its dependencies.

  2. Check your browser’s developer console for JavaScript errors that prevent the RTE from loading.

  3. Verify that all required client libraries for the Content Fragment Editor and RTE are present and loading.

    • Open the browser’s developer tools and inspect the Network tab while loading the Content Fragment Editor.
    • Look for failed requests related to client libraries, such as .js or .css files associated with the editor.
    • If client libraries are missing, verify that the relevant client libraries are properly deployed and accessible.

  4. Review your CORS (Cross-Origin Resource Sharing) configuration in AEM.

    • Verify that experience.adobe.com is included as an allowed origin.
    • Confirm that all relevant paths used by the Content Fragment Editor are included in the allowed paths.

  5. Check your Referrer Filter configuration.

    • Add regular expressions for allowed hosts, such as https://.*.adobe.com:443, under allow.hosts.regexp.
    • Set the allow.empty property to false if it isn’t already set.

  6. Verify that no permission or access issues prevent RTE resources from loading.

  7. Collect relevant logs for further analysis.

    • Download AEM error and access logs from the time of the issue.
    • Capture browser console logs and any failed network requests.

  8. Test with a supported browser and verify that it’s up to date, as browser compatibility can affect editor loading.

  9. After making configuration changes, reload the Content Fragment Editor

recommendation-more-help
experience-cloud-kcs-help-kbarticles