Premkarthic AEM-6.2-Communities-LiveFyre-Feature-Pack-3 is this
In the details tab of package share, you'll see that it is version
1.10.167. You should also be able to locate that same version of the
communities package in package manager of your AEM instance. Declare the
build dependencies in the pom using the same version as
This is not correct - do not use individual communities jars in your
dependency list since they are not available in public repos. JK
Kendall's advice is correct - use only the cq-socialcommunities-api jar
that corresponds to the communities-pkg installed in AEM, and place it
just before the AEM uber jar in the dependency list in the pom. Then
post your full build log here if you're still having problems.
social-blog does (did) create ugc in that the blog entries themselves
and the comments on the entries are ugc. It is not possible to get
social-blog to work on 6.2 since it uses "old style" replicated ugc and
6.2 and beyond only supports SRP style UGC. IIRC 6.1 was the last
version to support social-blog. The recommendation is to refactor the
application to either use social-journal which is publish-side blogging,
or implement blogging on the author node using normal AEM page
@brumoona87688495 if you have Communities FP5 or later installed, we've
discovered an incompatibility. Please see this
you do not have a Communities feature pack installed then the problem
may be different and that so...
Hi,We've confirmed that there is an incompatibility between Communities
FP5 and FP6 and the Invalidate Caches function. Communities FP5 requires
com.adobe.granite.ui.clientlibs.content-1.0.4.zip for some of the admin
ui screens. That package introduces a serviceuser "clientlibs-service"
for manipulating the /var/clientlibs directory. The
dumplibs.rebuild.html script in 6.1 which is in a different package does
not use the serviceuser, and is coded to remove the /var/clientlibs
directory during in...