Expand my Community achievements bar.

Join expert-led, customer-led sessions on Adobe Experience Manager Assets on August 20th at our Skill Exchange.
SOLVED

Setup with UE and AEM does not work - content is taken from demo project, not from AEM instance

Avatar

Level 2

Hello guys,

I finished the setup for EDS with Google Docs and it works like a charm.

Next step was to setup EDS with an AEM Cloud Instance. I went through all steps described here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/wy...

It did not humbled over any point, but changed content isn't reflected to any site, so I believe, that the project still points to the demo project and not my AEM instance.

 

Here are some information.

My GitHub project: https://github.com/PublicisMaikLindner/eds-with-ue-test

fstab.yaml:

Maikman831_0-1740477776917.png

path.json:

Maikman831_1-1740477867968.png

 

I changed and published the index site, but still the demo content is shown.

Also I added an additional site and published it, but it shows a 404 when I request this site:

Maikman831_2-1740478043248.png

 

I strongly believe, the GitHub-Project still show the demo content.

What can I check/change, to get my content behind the URL?

 

Best, Maik

 

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 2

Hi guys,

thanks for your effort.

The configuration was correct all the time, but we noticed that publishing of content didn't work.

After long talk with the support we get this answer:

 

The code sync for the fstab.yaml file hadn’t gone through, so the site was still pointing to the AEM Author environment used for the aem-boilerplate-xwalk. Engineering has now triggered the code sync, and a new content bus has been created for the site

 

That fixed the issue and publishing worked and I saw my content and not the demo content.

So in the end there was nothing we could do on our side.

 

Best, Maik

View solution in original post

3 Replies

Avatar

Administrator

@BrianKasingli @josephambrose @DarpanAn2 If you have a moment, please review this question and see if you can help. Thanks in advance!



Kautuk Sahni

Avatar

Level 8

Hi @Maikman831 ,

I think includes section is missing in your path.json 

"includes:" [
    "/content/eds-with-ue-test-by-maikman83/"
  ]

 Could you try adding this and publishing the pages?

Avatar

Correct answer by
Level 2

Hi guys,

thanks for your effort.

The configuration was correct all the time, but we noticed that publishing of content didn't work.

After long talk with the support we get this answer:

 

The code sync for the fstab.yaml file hadn’t gone through, so the site was still pointing to the AEM Author environment used for the aem-boilerplate-xwalk. Engineering has now triggered the code sync, and a new content bus has been created for the site

 

That fixed the issue and publishing worked and I saw my content and not the demo content.

So in the end there was nothing we could do on our side.

 

Best, Maik