Error | Community
Skip to main content
U
user06615
Level 2
April 20, 2022
Solved

Error

  • April 20, 2022
  • 1 reply
  • 794 views

{"file_path":"/var/log/aem/error.log","orig_time":"07.02.2022 07:36:07.921","level":"ERROR","msg":"[130.176.157.157 [1644219367526] GET /content/xyz/us/en/products/ovens/bov650.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource JcrNodeResource, type=xyz/components/breville/subscriptionlist, superType=null, path=/content/xyz/en/productpage/jcr:content/root/container/container/{xz}/subscriptonList" }

 

i am getting this above error in log

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 Prince_Shivhare

Hi,

The error can have multiple reasons. to debug the issue we usually follow different steps. with the above error, you can follow the below steps -

i) Take a backup of the content.

ii) set up some project-specific error and debug logs.

iii) Go to the path - /content/xyz/en/productpage/jcr:content/root/container/container/{xz}/subscriptonList and look for resourceType and follow the path accordingly. and check if the component is available.

iv) let's say if the component is available but still you are getting the error, then try to delete the node since you already have a backup so don't worry about that. and check if you are getting the same type of error for different nodes.

v) If you are not getting any errors then try to create a fresh page and drag and drop the same component and re-author it to understand and narrow down the issue.

 

Please let me know if you find something with the above steps.

Thank you,

Prince

1 reply

Prince_Shivhare
Community Advisor
Prince_ShivhareCommunity AdvisorAccepted solution
Community Advisor
April 20, 2022

Hi,

The error can have multiple reasons. to debug the issue we usually follow different steps. with the above error, you can follow the below steps -

i) Take a backup of the content.

ii) set up some project-specific error and debug logs.

iii) Go to the path - /content/xyz/en/productpage/jcr:content/root/container/container/{xz}/subscriptonList and look for resourceType and follow the path accordingly. and check if the component is available.

iv) let's say if the component is available but still you are getting the error, then try to delete the node since you already have a backup so don't worry about that. and check if you are getting the same type of error for different nodes.

v) If you are not getting any errors then try to create a fresh page and drag and drop the same component and re-author it to understand and narrow down the issue.

 

Please let me know if you find something with the above steps.

Thank you,

Prince

    Terms & ConditionsAccessibility statement

    Loading footer...