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:
path.json:
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:
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
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
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
@BrianKasingli @josephambrose @DarpanAn2 If you have a moment, please review this question and see if you can help. Thanks in advance!
Views
Replies
Total Likes
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?
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
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies