We have seen a lot of nodes that do not have a sling:resourceType or has incorrect value. These are mostly those nodes which were copied using the copy option on the page. The actual component had all details but on copying somehow the resource type value was getting lost or not copied.
We get error for these nodes:
No renderer for extension html, cannot render resource Paragraph, path=/content/project/master-blueprint/en/article/topics/treatment/jcr:content/par/featuretable_1643404036, type=nt:unstructured, cssClass=default, column=0/0, diffInfo=[null], resource=[JcrNodeResource, type=nt:unstructured, superType=null, path=/content/project/master-blueprint/en/article/topics/treatment/jcr:content/par/featuretable_1643404036]
These are not specific to certain components, rather a handful of the components are affected.
We recently tried to copy paste a component instance but were not able to replicate the issue. The node got copied well. We have recently used groovy and corrected all such nodes. On rechecking the logs again after a month we see the same error back again but for new occurrences.
The copied node names are usually in pattern: componentName_copy_someNumber
Cannot exactly pin point what is the issue. Suggestions will be helpful.
Hi @Shaheena_Sheikh,
We have faced similar issue: and found some older versions of AEM or specific builds (especially AEM 6.4/6.5 pre-SPs) had intermittent bugs where copy-paste dropped metadata like sling:resourceType.
You already did this:
Run a Groovy script to fix missing sling:resourceType fields in the repository.
In my case we have implemented custom workflow to Auto-Heal.
Views
Replies
Total Likes
Hi @Shaheena_Sheikh ,
Can you confirm which AEM version and Service Pack you are using?
Would request you to please update it to the latest.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies