Troubleshooting content fragment editor initialization errors in AEM
Attempts to edit content fragments in Adobe Experience Manager as a Cloud Service (AEMaaCS) default to the new content fragment editor, which fails to load with the error Failed to initialize app. To resolve this, update your CORS policy to allow experience.adobe.com, adjust Referrer Filter settings, and verify all required paths and hosts are configured correctly.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) – Sites
Issue/Symptoms
- Editing any content fragment launches the new content fragment editor by default.
- The editor fails to initialize and displaysFailed to initialize app.
- Browser console shows CORS errors indicating missing Access-Control-Allow-Origin headers for requests from experience.adobe.com.
- AEM logs show Referrer Filter rejections for POST requests involving endpoints such as /adobe/sites/cf/permissions and /adobe/sites/cf/graphql.
- Attempts result in 401 errors when fetching permissions.
Resolution resolution
To resolve this issue, follow these steps:
-
Review your current CORS configuration in AEM.
-
Add experience.adobe.com as an allowed origin in your CORS policy.
-
Ensure all relevant paths used by the content fragment editor are included in allowed paths within your CORS policy.
-
Review your Referrer Filter configuration.
-
Add regular expressions for allowed hosts under allow.hosts.regexp, including:
https://.*\.adobe.com:443https://.*\.adobe.net:443https://.*\.workfront.com:443https://.*\.workfront-dev.com:443https://.*\.dev.workfront.tech:443
-
Set allow.empty property in Referrer Filter configuration to false if not already set.
-
Save and deploy these configuration changes.
-
Attempt to edit a content fragment again using the new editor.
-
Verify that the editor loads successfully without displaying initialization errors.