Nothing shows in local AEM publish instance | Community
Skip to main content
E
eamon-zhang
Level 2
January 3, 2024
Solved

Nothing shows in local AEM publish instance

  • January 3, 2024
  • 3 replies
  • 2197 views

Hi,

I'm new on the AEM. I'm facing an issue in my local environment, can anyone help on this? Thanks a lot!

I've set local environment and created new AEM project, and installed the AEM WKND Sites, everything is fine, no errors occurred.

But when I tried to visit the page(already published) from publish instance (http://localhost:4503/content/wknd/us/en/about-us.html), it shown nothing on page. I checked the page source, it's nothing. I checked the page in CRXDE, everything looks fine. what's the problem on my AEM?

 

 

 

 

this is my reference sites:

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/aem-runtime.html

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/overview.html

https://github.com/adobe/aem-guides-wknd

 

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 aanchal-sikka

@eamon-zhang 

 

WKND bundles and /apps/wknd should be available on publish for pages to render.

Please assure, that you have installed same packages on Author and publish instance.

 

 

Even if we push content from author to publish. The Code still needs to be present on author and publish both.

 

Please assure you install the WKND all on publish as well

3 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
January 3, 2024

@eamon-zhang 

 

Can you possibly share

 

Or Pages to render you would need to assure following:

- The all package is also installed along with COntent 

- The WKND version is compatible with your AEM version. Details here: GitHub - adobe/aem-guides-wknd: Tutorial Code companion for Getting Started Developing with AEM Sites WKND Tutorial

 

 

Aanchal Sikka
E
eamon-zhangAuthor
Level 2
January 3, 2024

Hi @aanchal-sikka thanks for your response, I can't find the WKND bundle from 4503 instance, but I can see it in author(4502) instance, below is the details.

btw, I saw another post to ask the same issue, it says to check Sling GET servlet configuration at 
http://<host>:<port>/system/console/configMgr/org.apache.sling.servlets.get.DefaultGetServlet

Make sure that Enable JSON and Enable XML are selected.

I checked in 4503 instance, then visit the page http://localhost:4503/content/wknd/us/en/about-us.html, it shows the nodes directly, not the HTML.

 

 

I also check the error.log (4503 publish instance), here is the error log details:

 

03.01.2024 12:08:59.392 *WARN* [[0:0:0:0:0:0:0:1] [1704254939382] GET /content/wknd/us/en/about-us.html HTTP/1.1] com.day.cq.wcm.core.impl.page.PageImpl page at /content/wknd/us/en does not have a jcr:content childresource


03.01.2024 12:08:59.393 *WARN* [[0:0:0:0:0:0:0:1] [1704254939382] GET /content/wknd/us/en/about-us.html HTTP/1.1] com.day.cq.wcm.core.impl.page.PageImpl page at /content/wknd does not have a jcr:content childresource

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity AdvisorAccepted solution
Community Advisor
January 3, 2024

@eamon-zhang 

 

WKND bundles and /apps/wknd should be available on publish for pages to render.

Please assure, that you have installed same packages on Author and publish instance.

 

 

Even if we push content from author to publish. The Code still needs to be present on author and publish both.

 

Please assure you install the WKND all on publish as well

Aanchal Sikka
SureshDhulipudi
Community Advisor
SureshDhulipudiCommunity Advisor
Community Advisor
January 3, 2024

Check logs for any errors - it will show the missing references.

E
eamon-zhangAuthor
Level 2
January 3, 2024

thanks for your reply, it's solved.

as @aanchal-sikka said, need to install the WKND all on publish instance as well.

Madhur-Madan
Community Advisor
Madhur-MadanCommunity Advisor
Community Advisor
January 3, 2024

Hi @eamon-zhang ,

Looks like your code is only present on author and not on publish.
Push the code to publish instance using 'mvn clean install -PautoInstallPackagePublish'. This should fix your issue

E
eamon-zhangAuthor
Level 2
January 3, 2024

thanks for you reply. I've installed the package manually to publish instance.

yes, command line is good way to deploy the code to publish instance.

Terms & ConditionsAccessibility statement

Loading footer...