In AEM as a cloud getting the following error "No renderer for extension html, cannot render resource Paragraph" | Community
Skip to main content
R
RahulVo
Level 2
October 24, 2024
Solved

In AEM as a cloud getting the following error "No renderer for extension html, cannot render resource Paragraph"

  • October 24, 2024
  • 3 replies
  • 1174 views

I am using AEM Cloud and we are getting the below error and is happening on most of the pages  and Adobe has highlighted in the pro active notification to solve this. Any suggestion on how this can be fixed.

 

 


21.10.2024 00:08:05.694 [cm-p108388-e1076202-aem-author-55b6c696b9-vpdsd] *ERROR* [24.239.138.59 [1729469285226] GET /content/suncorp/businesspartners/en/home/policy/retail/security.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource Paragraph, path=/content/suncorp/businesspartners/en/home/reference-pages/policy-ref/rlg-nav/jcr:content/par/canvas/pars/content_container_1605405296, type=nt:unstructured, cssClass=default, column=0/0, diffInfo=[null], resource=[JcrNodeResource, type=nt:unstructured, superType=null, path=/content/suncorp/businesspartners/en/home/reference-pages/policy-ref/rlg-nav/jcr:content/par/canvas/pars/content_container_1605405296]
21.10.2024 00:08:05.695 [cm-p108388-e1076202-aem-author-55b6c696b9-vpdsd] *ERROR* [24.239.138.59 [1729469285226] GET /content/suncorp/businesspartners/en/home/policy/retail/security.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource Paragraph, path=/content/suncorp/businesspartners/en/home/reference-pages/policy-ref/rlg-nav/jcr:content/par/canvas/pars/content_container_1102807329, type=nt:unstructured, cssClass=default, column=0/0, diffInfo=[null], resource=[JcrNodeResource, type=nt:unstructured, superType=null, path=/content/suncorp/businesspartners/en/home/reference-pages/policy-ref/rlg-nav/jcr:content/par/canvas/pars/content_container_1102807329]

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 joerghoh

To validate this situation, you can use the servlet resolver (http://localhost:4502/system/console/servletresolver) to better understand, how Sling is doing that resolution.

 

 

3 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
October 24, 2024

 

resource=[JcrNodeResource, type=nt:unstructured, superType=null, path=/content/suncorp/businesspartners/en/home/reference-pages/policy-ref/rlg-nav/jcr:content/par/canvas/pars/content_container_1102807329]

This the candidate.
It's the node /content/suncorp/businesspartners/en/home/reference-pages/policy-ref/rlg-nav/jcr:content/par/canvas/pars/content_container_1102807329 and for the resource type "nt:unstructured" there is no rendering script available.

 

That sounds strange in the first place; but if a node has no "sling:resourceType" property defined, Sling will fallback to the JCR nodetype as the resource type. And basically this happens here: this node has not resource type defined.

 

 

 

 

 

 

    R
    RahulVoAuthor
    Level 2
    October 25, 2024

    And this is happening on multiple pages for almost all the components.

      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      October 26, 2024

      To validate this situation, you can use the servlet resolver (http://localhost:4502/system/console/servletresolver) to better understand, how Sling is doing that resolution.

       

       

        Dipti_Chauhan
        Community Advisor
        Dipti_ChauhanCommunity Advisor
        Community Advisor
        October 28, 2024

        Hi

         Also Check Sling GET servlet configurtaion at http://<host>:<port>/system/console/configMgr/org.apache.sling.servlets.get.DefaultGetServlet

        And check if Enable JSON and Enable XML are selected

          R
          RahulVoAuthor
          Level 2
          October 28, 2024

          Hi Dipti, 

          Yes, JSON and XML are enabled. 

            Terms & ConditionsAccessibility statement

            Loading footer...