Page Blank en.html | Community
Skip to main content
L
LKAemNewbie
New Member
December 12, 2023
Solved

Page Blank en.html

  • December 12, 2023
  • 4 replies
  • 989 views

Hi,

 

We have created a project with below command and build was successful. Installed it into local aem using

mvn clean install -PautoInstallPackage

and published the site and page. But when we access the page http://localhost:4503/content/wknd/us/en.html on publish instance it is blank. 


mvn -B archetype:generate
-D archetypeGroupId=com.adobe.aem
-D archetypeArtifactId=aem-project-archetype
-D archetypeVersion=39
-D appTitle="WKND Sites Project"
-D appId="wknd"
-D groupId="com.adobe.aem.guides"
-D artifactId="aem-guides-wknd"
-D package="com.adobe.aem.guides.wknd"
-D version="0.0.1-SNAPSHOT"
-D aemVersion="cloud"

 

Tried below options and still the page is rendering blank. Please suggest.

 

- Restarted aem instances

- In aem-guides-wknd POM.xml updated core.wcm.components.version to 2.23.4 from 2.19.0

- Tested replication agent connection and it is successful

- Checked in http://localhost:4502/system/console/bundles and are active and no errors

- Checked http://localhost:4502/crx/packmgr and all packages are green and installed

- Checked publish error.log and found below error

 

GET /content/wknd/us/en.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=wknd/components/page, superType=null, path=/content/wknd/us/en/jcr:content

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 divanshug


Hello @lkaemnewbie 

 

I encountered a similar issue previously. Upon investigation, I discovered that the Java version in use was a critical factor. My AEM instance was initially running on Java 8, and the problem persisted until I transitioned to an instance running on Java 11, upon which I successfully deployed the archetype.

 

However, I would recommend addressing this issue by closely examining the error message. It suggests that the jcr:content node might be referencing a non-existent resource type. Therefore, it would be prudent to follow the Sling resolution process and thoroughly validate the rendering chain for potential discrepancies.

 

Best regards,
Divanshu

 

4 replies

divanshug
Adobe Champion
divanshugAdobe ChampionAccepted solution
Adobe Champion
December 12, 2023


Hello @lkaemnewbie 

 

I encountered a similar issue previously. Upon investigation, I discovered that the Java version in use was a critical factor. My AEM instance was initially running on Java 8, and the problem persisted until I transitioned to an instance running on Java 11, upon which I successfully deployed the archetype.

 

However, I would recommend addressing this issue by closely examining the error message. It suggests that the jcr:content node might be referencing a non-existent resource type. Therefore, it would be prudent to follow the Sling resolution process and thoroughly validate the rendering chain for potential discrepancies.

 

Best regards,
Divanshu

 

    M
    Mahesh_Gunaje
    Level 7
    December 12, 2023

    @lkaemnewbie 

    I hope page is loading fine in Author environment. check the jcr:node in publish environment. 1 or multiple inner jcr node is corrupted. I mean there might be node under en/jcr:content which does not have proper details.

      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity Advisor
      Community Advisor
      December 12, 2023

      Hello @lkaemnewbie 

      1. The following command would only create a new project. It is not the same as WKND

      mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=39 -D appTitle="WKND Sites Project" -D appId="wknd" -D groupId="com.adobe.aem.guides" -D artifactId="aem-guides-wknd" -D package="com.adobe.aem.guides.wknd" -D version="0.0.1-SNAPSHOT" -D aemVersion="cloud"

      It is just a basic recommended set-up, on which you create a site. It would have proxy components which you can add and author content.

      • Set up author
      • Create pages
      • Add content
      • Publish page
      • You should now be able to see content on publish

      2. You would need to add clientlibs to have desired look n feel

      3. The latest archtype is 47. Please consider using latest https://github.com/adobe/aem-project-archetype

      4. For Actual WKND site, please download the src from https://github.com/adobe/aem-guides-wknd

       

       

      Aanchal Sikka
        Sudheer_Sundalam
        Community Advisor
        Sudheer_SundalamCommunity Advisor
        Community Advisor
        December 12, 2023

        @lkaemnewbie ,

        Run 

        mvn clean install -PautoInstallPackagePublish

        to build and install the code and content packages to publish instance.

        You can also use

        mvn clean install -PautoInstallPackage,-PautoInstallPackagePublish

        to install to both author and publish at the same time.

         

        Hope this helps! 

          Terms & ConditionsAccessibility statement

          Loading footer...