A DevOps engineer sees a blank page and the log says 'No renderer for extension html'. What is a potential cause?

A DevOps engineer sees a blank page and the log says 'No renderer for extension html'. What is a potential cause?

• A. The apache dispatcher does not send the correct format header.
• B. The path for the resource type as declared by the content node does not exist.
• C. The resource super type declaration is missing on the content node.
• D. The content path is not configured to deliver HTML renderings.

Answer: (B)

Rendering in Sling/AEM hinges on the resource type declared on the content node. When a request comes in for HTML, Sling looks for a renderer script that matches that resource type. If the path specified for the resource type no longer exists (for example, the component was moved or deleted and the resourceType points to a non-existent location), there’s no render script to handle the HTML extension. That lack of a renderer leads to the blank page and the log message “No renderer for extension html.” So the most likely cause is that the path for the resource type declared by the content node does not exist. To fix it, verify the sling:resourceType on the content node and ensure the corresponding component exists under /apps or /libs with the proper HTML renderer script. The other options would produce different symptoms, such as header mismatches or missing rendering scripts unrelated to an missing resource type path.

Rendering in Sling/AEM hinges on the resource type declared on the content node. When a request comes in for HTML, Sling looks for a renderer script that matches that resource type. If the path specified for the resource type no longer exists (for example, the component was moved or deleted and the resourceType points to a non-existent location), there’s no render script to handle the HTML extension. That lack of a renderer leads to the blank page and the log message “No renderer for extension html.”

So the most likely cause is that the path for the resource type declared by the content node does not exist. To fix it, verify the sling:resourceType on the content node and ensure the corresponding component exists under /apps or /libs with the proper HTML renderer script. The other options would produce different symptoms, such as header mismatches or missing rendering scripts unrelated to an missing resource type path.