No renderer for extension html, cannot render resource JcrNodeResource | Community
Skip to main content
P
prasanth_s
New Participant
November 3, 2023
Solved

No renderer for extension html, cannot render resource JcrNodeResource

  • November 3, 2023
  • 5 replies
  • 6204 views

I am using AEM 6.5 , service package 6.5.17. Its a AEM SPA with React project. After creating a custom component and integrated with react component for the same, on loading the AEM page, getting white screen and facing the below error in errors.log file -

*ERROR* [[0:0:0:0:0:0:0:1] [1699013725876] GET /editor.html/content/projectname/projectsubname/us/en/home.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=fd/af/authoring/editors/rendercondition/form-v2, superType=null, path=/libs/cq/gui/content/editor/form-v2/granite:rendercondition

*ERROR* [[0:0:0:0:0:0:0:1] [1699013725876] GET /editor.html/content/projectname/projectsubname/us/en/home.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=fd/af/authoring/editors/rendercondition/template-v2, superType=null, path=/libs/cq/gui/content/editor/formtemplate-v2/granite:rendercondition

Also unable to see any parsys on the page in editor mode. (No console error). Kindly let me know if any further information required. Please advise me on this to resolve the error.
Thanks

    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 kautuk_sahni

    The error message "No renderer for extension html, cannot render resource JcrNodeResource" indicates that AEM cannot find a suitable renderer to process the requested resource. This can happen for a few reasons:

    The resource type is not registered: AEM uses resource types to determine which renderer to use for a particular resource. If the resource type is not registered, AEM will not be able to find a renderer and will throw this error.

    The renderer is not available: Even if the resource type is registered, the renderer might not be available if it is not deployed or if there is a problem with its configuration.

    There is a conflict between renderers: If there are multiple renderers registered for the same resource type, AEM might not be able to choose the correct one, resulting in this error.

    In this case, the error is occurring for two resource types: fd/af/authoring/editors/rendercondition/form-v2 and fd/af/authoring/editors/rendercondition/template-v2. These resource types are likely part of the AEM authoring UI, and the error suggests that there is a problem with the renderers for these resource types.

    Here are a few possible solutions to the problem:

    • Restart AEM: Sometimes, AEM can get into a state where it is unable to properly resolve renderers. Restarting AEM can sometimes fix this problem.

    • Check the Sling Resource Resolver: The Sling Resource Resolver is responsible for mapping resource paths to resource objects. If there is a problem with the Sling Resource Resolver, AEM might not be able to find the correct renderer for a resource. You can check the Sling Resource Resolver configuration in the OSGi console.

    • Check the renderer configuration: The configuration of the renderers for the fd/af/authoring/editors/rendercondition/form-v2 and fd/af/authoring/editors/rendercondition/template-v2 resource types might be incorrect. You can check the configuration of these renderers in the OSGi console.

    • Check for conflicts between renderers: If there are multiple renderers registered for the same resource type, AEM might not be able to choose the correct one. You can check for conflicts between renderers in the OSGi console.

    5 replies

    L
    leek86608325
    New Participant
    May 14, 2024

    Until AEM fixes this with another service pack, I believe it's just a stale pointer in /libs that was missed. I fixed this temporarily by adding the following files to my ui.apps module, with the .jsp files having the same content as their non-v2 counterparts in /libs. Make sure to add the parent to ui.apps.structure/pom.xml and the child folders to your ui.apps filter. 

     

     

    L
    LyleX
    New Participant
    March 23, 2024

    Hi @prasanth_s ,

     

    Have a good day, I am also using 7.5.17 and encountered the same error. Have you solved it? Can you share the solution?

      L
      leek86608325
      New Participant
      May 14, 2024

      I am also encountering this error. Why would AEM be calling this renderCondition resource if it doesn't exist?

      kautuk_sahni
      kautuk_sahni
      Employee
      November 14, 2023

      @prasanth_s Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

      Kautuk Sahni
      kautuk_sahni
      kautuk_sahniAccepted solution
      Employee
      November 9, 2023

      The error message "No renderer for extension html, cannot render resource JcrNodeResource" indicates that AEM cannot find a suitable renderer to process the requested resource. This can happen for a few reasons:

      The resource type is not registered: AEM uses resource types to determine which renderer to use for a particular resource. If the resource type is not registered, AEM will not be able to find a renderer and will throw this error.

      The renderer is not available: Even if the resource type is registered, the renderer might not be available if it is not deployed or if there is a problem with its configuration.

      There is a conflict between renderers: If there are multiple renderers registered for the same resource type, AEM might not be able to choose the correct one, resulting in this error.

      In this case, the error is occurring for two resource types: fd/af/authoring/editors/rendercondition/form-v2 and fd/af/authoring/editors/rendercondition/template-v2. These resource types are likely part of the AEM authoring UI, and the error suggests that there is a problem with the renderers for these resource types.

      Here are a few possible solutions to the problem:

      • Restart AEM: Sometimes, AEM can get into a state where it is unable to properly resolve renderers. Restarting AEM can sometimes fix this problem.

      • Check the Sling Resource Resolver: The Sling Resource Resolver is responsible for mapping resource paths to resource objects. If there is a problem with the Sling Resource Resolver, AEM might not be able to find the correct renderer for a resource. You can check the Sling Resource Resolver configuration in the OSGi console.

      • Check the renderer configuration: The configuration of the renderers for the fd/af/authoring/editors/rendercondition/form-v2 and fd/af/authoring/editors/rendercondition/template-v2 resource types might be incorrect. You can check the configuration of these renderers in the OSGi console.

      • Check for conflicts between renderers: If there are multiple renderers registered for the same resource type, AEM might not be able to choose the correct one. You can check for conflicts between renderers in the OSGi console.

      Kautuk Sahni
      L
      LyleX
      New Participant
      March 23, 2024

      Hi @kautuk_sahni ,

      I can't find resource fd/af/authoring/editors/rendercondition/form-v2 and fd/af/authoring/editors/rendercondition/template-v2 in /libs/fd/af/authoring/editors/rendercondition node, please have check and AEM version 6.5.17.

       

      So this is maybe a error quote.

       

       

       

        EstebanBustamante
        EstebanBustamante
        New Participant
        November 3, 2023

        Could you try restarting your instance? Usually, this error disappears after a reboot.

        Esteban Bustamante
          P
          prasanth_sAuthor
          New Participant
          November 4, 2023

          Hi @estebanbustamante ,

          The restart of the instance also not working. Whether it could be due to the page contains other components which are not mapped to the react component of the same or missing sling model for the components? Since even the parsys to drag components is not visible.

            Terms & ConditionsAccessibility statement

            Loading footer...