Universal Editor cannot open AEM Cloud page | Community
Skip to main content
M
mpmuradov
Level 2
May 15, 2025
Solved

Universal Editor cannot open AEM Cloud page

  • May 15, 2025
  • 4 replies
  • 1082 views

Hi here!

 

I tried to use Universal Editor with a page hosted in AEM Cloud (not locally). But UE cannot open the page.

Accorded to this doc https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/getting-started I instrumented WKND page component. I put this

<script src="https://universal-editor-service.adobe.io/cors.js" async></script>
<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com/">

to `customheaderlibs.html` and I see in preview mode it was applied.

But UE doesn't recognize the page. I went here https://experience.adobe.com/#/@smartlingexchange/home opened `Experience Manager` -> `Universal Editor`, put link to the page https://author-p15353-e35406.adobeaemcloud.com/content/wknd/language-masters/en/test-editor.html?wcmmode=disabled and launched the editor. It shows `Ooops` page

Did I missed something?

 

Any help is appreciated.

Thank you!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by muskaanchandwani

Hello @mpmuradov 

Could you please try to remove the trailing slash from the instance URL in the meta tag?

<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com/">

to

<meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com">

4 replies

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
May 15, 2025

Hi @mpmuradov,

Can you make sure:

  • This is injected into the final rendered page.

  • Open the page (test-editor.html) in the browser, do View Source, and verify both tags are visible there (not stripped by a proxy or CDN).

  • This must be done only on the author instance – not on publish.

1. CORS Support

AEM must allow the Universal Editor service (https://universal-editor-service.adobe.io) through its CORS policy. You need to verify the AEM Cloud's

1. CORS configuration:

  • In AEM Cloud, the dispatcher/CDN rules may block cors.js or not include the correct Access-Control-Allow-Origin headers.

  • Check whether CORS is set up in the cdn.yaml or dispatcher config to allow this origin:

    - origin: https://universal-editor-service.adobe.io methods: [GET] headers: ["*"]
2. Document Type & Model Configuration

UE only works with structured content pages that are backed by a document type / content fragment model. If your page (test-editor.html) doesn’t use a model declared in UE config, it won't open.

  • Has your page been registered in the UE via the appropriate JSON model or fragment model?

  • Check if your page has structured content using a content model that is UE-enabled.

3. Universal Editor Configuration in Admin Console

Check if your AEM environment is correctly mapped in UE:

  • Go to Adobe Admin Console > Product Configurations > Universal Editor.

  • Verify that the mapping for your domain author-p15353-e35406.adobeaemcloud.com exists.

  • You might need Adobe support to ensure your environment is UE-enabled.

If you're testing with the WKND site, try using this known working path:

https://author-<your-env>.adobeaemcloud.com/content/wknd/language-masters/en/magazine.html

That page is component-backed and already has structure.

Hope that helps!

Santosh Sai
    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    May 16, 2025

    Hi @mpmuradov ,

    Follow all the steps below. These ensure your page is structurally editable, CORS-compliant, and correctly configured for Universal Editor.

      arunpatidar
      Community Advisor
      arunpatidarCommunity Advisor
      Community Advisor
      May 16, 2025

      Hi @mpmuradov 

      The issue could be that UE is not able to communicate with AEM due to 3rd party cookie restriction.

      Try in Chrome, normal window(not incognito) and check if error is gone or having other error. 

      Arun Patidar
        muskaanchandwani
        Adobe Employee
        muskaanchandwaniAdobe EmployeeAccepted solution
        Adobe Employee
        May 16, 2025

        Hello @mpmuradov 

        Could you please try to remove the trailing slash from the instance URL in the meta tag?

        <meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com/">

        to

        <meta name="urn:adobe:aue:system:aemconnection" content="aem:https://author-p15353-e35406.adobeaemcloud.com">
          Supriya_Savre
          Supriya_Savre
          Level 4
          May 20, 2025

          Hi @mpmuradov,

          Did the shared solution help you out? If yes, kindly consider marking the most suitable answer as ‘correct’.

          If you’re still facing any challenges, please feel free to continue the conversation here. We’re happy to support further.

          Terms & ConditionsAccessibility statement

          Loading footer...