Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Nothing shows in local AEM publish instance

Avatar

Level 2

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?

eamonzhang_1-1704246313760.png

 

eamonzhang_0-1704246117766.png

 

 

 

this is my reference sites:

https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/local-development-env...

https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetyp...

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

 

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@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

View solution in original post

8 Replies

Avatar

Community Advisor

@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 Site...

aanchalsikka_0-1704250588089.png

 

 


Aanchal Sikka

Avatar

Level 2

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.

eamonzhang_0-1704253813604.png

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.

eamonzhang_4-1704254787713.png

 

eamonzhang_2-1704254508946.png

 

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

Avatar

Correct answer by
Community Advisor

@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

Avatar

Level 2

you're right, that's the root cause. I upload the package and install to publish, it works now.

no need to change the Sling GET servlet configuration of "org.apache.sling.servlets.get.DefaultGetServlet"

thanks!

eamonzhang_0-1704262771310.png

 

Avatar

Community Advisor

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

Avatar

Level 2

thanks for your reply, it's solved.

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

Avatar

Level 5

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

Avatar

Level 2

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.