No results found. is the message I am getting.Also I could see the
package is available in some internal/private repository from the URL
shared (content/companies/private/day_internal/packages/adobe/cq600). Is
there any way to get the package.
This link is not opening for me. Getting the error as below."Sorry, an
error occurred while processing your request.Please contact
cqcloud@adobe.com with your Adobe ID to report the problem."
I am not able to find the hotfix package location for the hotfix Adobe
Experience Manager Hotfix Package NPR-8606:1.1.I was added as a
dependency for cq-6.0.0-hotfix-10767
(https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/packages/cq600/hotfix/cq-6.0.0-hotfix-10767).Any
suggestion would help.
In AEM landing page feature, we are using relative path in JS file.For
example loadFile(js/chapter1/1.json, true);.Relative path in HTML files
are automatically handled and converted into absolute path
(etc/.../js...).Is there any way to handle relative to absolute path
conversion for the uploaded JS file?
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/companies/public/adobe/packages/cq610/social/hotfix/cq-socialcommunities-pkg
This hotfix is necessary to resolve the issue even if you're not using
Communities features. ...
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 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....
