Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Resource Resolver returns an additional Resource in AEM 6.1

Avatar

Level 2

I am trying to find the resources using Resource Resolver. Below is the sample code which I am using. I am getting the Resolver from the the request.

Iterator<Resource> resources = resourceResolver.findResources(query, Query.JCR_SQL2);

The above code returns the additional resource called com.adobe.cq.social.datastore.jcr.impl.SocialResourceWrapper in additional to the expected one.

Please suggest how to resolve this.

This issue occurs when we try to migrate from AEM 6.0 to 6.1. Same code works fine in AEM 6.0

1 Accepted Solution

Avatar

Correct answer by
Employee

This sounds familiar. I believe it is a bug that has already been fixed. Please verify in packagemanager if you're running cq-socialcommunities-pkg 1.7.197, and if so then apply a hotfix version 1.7.199 available here:

https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/compani...

This hotfix is necessary to resolve the issue even if you're not using Communities features.

Regards,

Don

View solution in original post

2 Replies

Avatar

Correct answer by
Employee

This sounds familiar. I believe it is a bug that has already been fixed. Please verify in packagemanager if you're running cq-socialcommunities-pkg 1.7.197, and if so then apply a hotfix version 1.7.199 available here:

https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/compani...

This hotfix is necessary to resolve the issue even if you're not using Communities features.

Regards,

Don

Avatar

Level 2

dwalling wrote...

This sounds familiar. I believe it is a bug that has already been fixed. Please verify in packagemanager if you're running cq-socialcommunities-pkg 1.7.197, and if so then apply a hotfix version 1.7.199 available here:

https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/compani...

This hotfix is necessary to resolve the issue even if you're not using Communities features.

Regards,

Don

 

Installing Hot fix has resolved the issue. Thanks!!!