۶Ƶ Experience Manager: The first investigation step for “No renderer for extension html”
This article explains the cause of the error message: No renderer for extension html, encountered when attempting to open a webpage in ۶Ƶ Experience Manager.
Description description
Environment
-
۶Ƶ Experience Manager 6.5
-
۶Ƶ Experience Manager as a Cloud Service
Issue/Symptoms
You might encounter an error message with No renderer for extension html. This article will guide you through the initial checks to perform when this error arises.
Resolution resolution
The error message No renderer for extension html suggests that AEM cannot find the necessary script or program to render HTML content. As a result, this may lead to the failure of displaying parts of or the entire page.
Example:
01.01.2024 12:34:56.789 *ERROR* [ 192.168.0.123 [ 0000000000000] GET /content/wknd/us/en/testpage01.html HTTP/1.1] org.apache.sling.servlets.get.impl.DefaultGetServlet No renderer for extension html, cannot render resource TemplatedResourceImpl, type=wknd/components/missing, path=/content/wknd/us/en/testpage01/jcr:content/root/container/text
In the given example, the error suggests that when the page /content/wknd/us/en/testpage01.html
is accessed, certain components of the page cannot be rendered. Specifically, the resource wknd/components/missing, which is sling:resourceType
of the component at jcr:content/root/container/text on testpage01, is not found in AEM. Consequently, this results in the component being absent from the page.
The first step in addressing this error is to verify the presence of the resource, as denoted by the type wknd/components/missing in the given example, within AEM.