Hi ,
When I am going through the error log of my server noticed that major portion of the log is covered by a warning which states "Get /content/test/en_US/demoPage.html Http /1.1] core.day.cq.wcm.core.impl.page.PageImpl page at /content/test/en_US does not have a jcr:content childresource". Could anyone explain what will be the issue?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @nivethaS , Below are the explanation of your logs and solution.
Get /content/test/en_US/demoPage.html Http /1.1 :This indicates the HTTP request that was made to access the page. It specifies the URL path and the HTTP version used.
core.day.cq.wcm.core.impl.page.PageImpl: This implementation class in AEM that encountered the error. In this case, it is the PageImpl class, which is responsible for handling page-related operations.
page at /content/test/en_US: This indicates the path of the page that is causing the issue. In this case, the page is located at /content/test/en_US.
does not have a jcr:content childresource: This indicates the specific problem. It states that the page at /content/test/en_US does not have a child resource named jcr:content. In AEM, the jcr:content node is typically used to store the content and properties of a page.
Solution : You need to ensure that the page at /content/test/en_US has a child resource named jcr:content. This can be done by creating a new child node under the page node with the name jcr:content.
Regards,
Shiv
Hi @nivethaS , Below are the explanation of your logs and solution.
Get /content/test/en_US/demoPage.html Http /1.1 :This indicates the HTTP request that was made to access the page. It specifies the URL path and the HTTP version used.
core.day.cq.wcm.core.impl.page.PageImpl: This implementation class in AEM that encountered the error. In this case, it is the PageImpl class, which is responsible for handling page-related operations.
page at /content/test/en_US: This indicates the path of the page that is causing the issue. In this case, the page is located at /content/test/en_US.
does not have a jcr:content childresource: This indicates the specific problem. It states that the page at /content/test/en_US does not have a child resource named jcr:content. In AEM, the jcr:content node is typically used to store the content and properties of a page.
Solution : You need to ensure that the page at /content/test/en_US has a child resource named jcr:content. This can be done by creating a new child node under the page node with the name jcr:content.
Regards,
Shiv
Hi Nivetha,
The error means that the jcr:content node under the page node /content/test/en_US/demoPage is not there.
If this error is in publish then check if the jcr:content node is present in author and activate the page it will resolve the issue.
If this error is in author then you can create the jcr:content node.
@nivethaS Did you find the suggestion 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.
Views
Replies
Total Likes
Views
Likes
Replies