Premkarthic AEM-6.2-Communities-LiveFyre-Feature-Pack-3 is this
one:https://www.adobeaemcloud.com/content/marketplace/marketplaceProxy.html?packagePath=/content/companies/public/adobe/pack…
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
follows:com.adobe.cq.socialcq-socialcommunit...
What version of AEM are you using and what version of
cq-socialcommunities-pkg is installed in it? the api jar needs to match
the pkg version. api 1.9.236 and console 1.3.0 are not compatible.
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
authoring.
Are you using AEM Communities 6.1 or later? If yes, this is similar to
near-term roadmap features, and it would be worth contacting your sales
representative to engage in the featurepack process.
@brumoona87688495 if you have Communities FP5 or later installed, we've
discovered an incompatibility. Please see this
suggestion:http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.forum__98y7-im_having_troublere__kcrx-hi_weveconfirmed._s_1_tosp.html/forum__98y7-im_having_troublere.html#forum__98y7-im_having_troublere__kcrx-hi_weveconfirmedIf
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...
I hadn't read this article until you pointed it out, but its discussing
well-known concepts IMORegarding MSRP, the author_display_name field is
deprecated and no longer being used. It will likely be removed in a
future update. The reason is that architecturally we use the
authorizableId as the handle to the user info, and can separately handle
PII information that might be in a user profile separate from the UGC
which doesn't have PII. The authorizableId is the link between the two,
and we do th...
AEM Communities components are just normal components so they can be put
on any AEM page. But they're easiest to manage if you use the
Communities wizards. We generally recommend using the wizard to create
subsite or sub group areas under your page tree. The pages can be
customized with overlays in the /apps directory to achieve whatever
custom appearance/layout you like. Perhaps you can share a little more
detail about what you're trying to do and we can help moreDon
As general guidance, I would recommend using the profile tree in JCR
only for attributes that change infrequently like passwords, address,
possibly site preferences. These are things that are unlikely to change
during a given login session and perhaps only change a few times per
month or year. This will keep the load on SCD light and avoid an
potential bottleneck problems. Other attributes that will change during
a login session should be stored through the SRP APIs into the
configured SRP stora...
In AEM 6.0 were you using cloud storage for the blog or local JCR? If
cloud storage, then please contact Support and open an RFH ticket and we
can provide advice on how to migrate the blog to AEM 6.2 Journal using
the ugc migration utility here:
https://github.com/Adobe-Marketing-Cloud/aem-communities-ugc-migrationIf
you were using JCR storage then please note that replication of UGC
including blog/journa is no longer supported as of AEM 6.1. It is not
possible to use the 6.0 cq-social-blog comp...
You can use the migration utility here to export ugc that is in AEM into
a local
file:https://github.com/Adobe-Marketing-Cloud/aem-communities-ugc-migration
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-pkgThis
hotfix is necessary to resolve the issue even if you're not using
Communities features.Regards,Don
Hi Seetha,As of AEM 6.2, JSRP is supported for production use but only
for a mongodb cluster used on the publish nodes. A tarmk farm cannot use
JSRP and must continue to use either MSRP or ASRP. Further information
is
here:https://docs.adobe.com/docs/en/aem/6-2/deploy/communities/topologies.htmlRegards,Don
The Communities components including Reviews use AEM user nodes to
provide identity and ACL information. Does your integration with Janrain
create any user node in AEM, similar to the LDAP connector? If yes, then
you should be able to use the Communities component. If not, then indeed
it will require a lot of customization.
There are some code examples on github that might be usefulThe
beginnings of an "SRP Browser" tool:
https://github.com/Adobe-Marketing-Cloud/aem-communities-srp-browserA
tool to migrate UGC from 5.x versions to the "common store" SRP approach
in 6.1 and later:
https://github.com/Adobe-Marketing-Cloud/aem-communities-ugc-migrationA
repo for SRP tools, which currently contains one utility to clear out an
ASRP report suite:
https://github.com/Adobe-Marketing-Cloud/aem-communities-srp-toolsCode
samp...
Hi Seetha,The best option to achieve email notifications for activity in
a Community is to use the Communities FP1 for 6.2 which is currently
available as a buddy drop through your sales representative. Its due out
in just a few weeks, and has a much more robust email templating
approach than was in 5.x, support for notifications, subscriptions, and
email replies, and has a configurable notifications UI for users. It
will also be available as FP5 for AEM 6.1. Regards,Don
Yes, you can create your own components and respective endpoints to
respond to your components. You can use handlebars or other ui
frameworks such as react or angular, and you can choose to use SCF or
create your own backend components. It will be more work because you'll
be creating a lot of things from scratch, but if that is what your
project needs then it is definitely possible.That said, is there a
reason that SCF does not meet your needs? Is there an enhancement you'd
like to bring to our ...
Please be aware that many of the capabilities documented at
https://docs.adobe.com/docs/en/aem/6-0/administer/social-communities/social-plugins.html
are for 6.0 and have been deprecated and subsequently removed from AEM.
The recommendation is to use facebook and twitter APIs directly. It
hasn't been possible for us to thoroughly support integrations such as
facebook and twitter since AEM is released only once per year.
The AEM Communities featurepacks are usually available to all AEM
Communities customers. The 6.1 featurepack was temporarily removed from
packageshare to address an issue that was found after it was posted. A
replacement package is being tested right now and should be available
publicly very soon.
For 6.1 GM unfortunately using the deprecated SocialUtils is the only
option. There will be an upcoming Communities FP4 for 6.1 which will
offer the new APIs that will also be in 6.2.
One reason: ACLs on the pages are typically different than ACLs on the
UGC itself. Typically UGC can be edited by the original poster as well
as privileged users, whereas the corresponding pages cannot.Second, the
page nodes are always stored in JCR and only forward replicated. For UGC
nodes, in AEM 6.1 and beyond the UGC nodes are stored in a configured
SRP "common store". In AEM 6.0 and earlier, UGC nodes were reverse
replicated to author and then forward replicated to other publish nodes
in t...
There are no hard-coded limits to the number of forums and comments that
are supported in AEM Communities. The limitations will derive from the
topologies and storage approaches that are chosen for the project.
Millions of posts/comments in thousands of forums would be reasonably
achievable using either MSRP or ASRP in typical datacenter environments.
Integration of AEM with Jive is not a feature at the AEM product level.
It could be done through customization since both AEM and Jive provide
server endpoints for integration, but it would likely be a lot of work.
AEM offers content management and approval workflows as well as
community and collaboration features. In addition, AEM Communities 6.1
which is now available provides author-side tools to quickly create
communities. A discussion-based community with forums, private messages,
activitys...
When UGC is stored in JCR, it can be inspected by using CRXDE. It is not
supported to inspect or operate on the mongomk nodes directly as the
format or structure may change in future releases. Beginning with social
communities 1.4 which was available in 5.6.1 the recommended API to
interact with UGC is to use SCF or the sling resource provider API
directly. Using these APIs rather than JCR will allow components and
applications to continue to work independent of where UGC is stored. In
Communiti...
