Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

No renderer for extension html, cannot render resource Paragraph

Avatar

Avatar
Validate 1
Level 2
jond1978
Level 2

Likes

5 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile

Avatar
Validate 1
Level 2
jond1978
Level 2

Likes

5 likes

Total Posts

18 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile
jond1978
Level 2

15-10-2015

Hi,

While loading our pages in WCM Editor (6.1) , the following exception is being thrown.

*ERROR* [127.0.0.1 [1442943894925] GET /content/acme-global/acme-com/11.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource Paragraph, path=/content/acme-global/jcr:content/acme_footer/acmecontent, type=acme-foundation/components/content/ACMEContent, cssClass=default, column=0/0, diffInfo=[null], resource=[JcrNodeResource, type=acme-foundation/components/content/ACMEContent, superType=null, path=/content/acme-global/jcr:content/acme_footer/acmecontent]

Note:

We have added a Page.html.jsp in /libs/foundation/components/primary/cq/Page/ to handle the html extension. In the vanila installation of 6.1 Page.html.jsp was missing.

I don't have any clue for this issue other than adding the custom exception page. Your help is greatly appreciated.

Thanks in advance,

View Entire Topic

Avatar

Avatar
Shape 1
Employee
mahajanyogesh
Employee

Likes

6 likes

Total Posts

6 posts

Correct Reply

1 solution
Top badges earned
Shape 1
Give Back
Boost 5
Boost 3
Boost 1
View profile

Avatar
Shape 1
Employee
mahajanyogesh
Employee

Likes

6 likes

Total Posts

6 posts

Correct Reply

1 solution
Top badges earned
Shape 1
Give Back
Boost 5
Boost 3
Boost 1
View profile
mahajanyogesh
Employee

21-02-2019

This issue can occur due to one more reasons - Pasting a component from other page on a "new page". A empty node without resource type is generated in such cases. More explained in this link - AEM Resources missing sling:resourceType - Stack Overflow

The issue raised CQ-4212306 will be part of 6.4 release.