Hello, please file a DayCare ticket and the support organization will
download the update and make it available to you. We still intend to
push these updates to PackageShare eventually, but the current version
is not able to accommodate the load/volume, therefore we are working on
a new version (live this coming summer). Thank youBertrand de Coatpont -
Product Management - AEM
Hello, the Email notification templates are bound to a specific resource
type (not to a specific location/path), so out of the box there isn't a
way to configure different templates for your 3 pages.
It's meant to happen automatically with a background scheduled task.
Maybe you can setup a logger for
com.adobe.cq.social.commons.comments.scheduler.impl.SearchScheduledPosts
to check if this code path is executed or not (on publish). I would also
check if the AEM scheduler is functioning properly on Publish
It would also be interesting to check if it's working normally in a
regular Blog home page. (when using the Blog community function in a
Community Site). Dropping the sidebar components in some arbitrary page
is a very unusual scenario.
Yes - displaying badge (or not) is an option on each component. And
scoring/badging rules can be placed on individual components also,
please see Scoring and Badges Essentials
hi Rajeev,A few reasons come to mind, there might be more:- it allows
for ACLs to be set on the UGC tree independently from the ACLs on the
page tree (publish side users vs. author side users)- it allows for UGC
to be shared across multiple languages (see the "shared language store"
feature)- it allows for importing/exporting UGC independently from the
page treeBertrand
Can you please check if your dispatcher is configured as per the
documentation here:
https://docs.adobe.com/docs/en/aem/6-2/deploy/communities/dispatcher.htmlthank
youBertrand
On the first set of questions: With the demo machine, you first need to
download the We.Retail add-on, this will get you the latest release for
6.2 and 6.3 from GitHub.com, including for Communities area.Then you
need to make sure:- To set demo.communities.samples.weretail=true- To
select the We-Retail option when creating your demo environmentThere's
no dependency on service packs or cumulative fix packs to be installed
first, although it is recommended.On a vanilla instance, just look under
/l...
hi Sandeep,You need to use the SCF/SRP APIs to query Community content
(query builder won't
work)https://docs.adobe.com/docs/en/aem/6-2/develop/communities/scf.htmlThere's
plenty of samples on GitHub, e.g.
https://github.com/Adobe-Marketing-Cloud/aem-communities-srp-browserthanksBertrand
hello SandeepDSRP was added as part of a feature pack for 6.1 and 6.2 -
please make sure you download and install as
per:https://docs.adobe.com/docs/en/aem/6-2/deploy/communities.htmlBertrand
Hi Rama 1. Yes it is highly recommended to use Handlebars. since all
Communities components are using this templating mechanism - it allows
for isomorphic rendering (client side or server side) which is important
for applications with read/write interactions (
https://docs.adobe.com/docs/en/aem/6-2/develop/communities/scf.html )2.
Yes it is highly recommended to use SCF (Handlebars being it's
presentation layer) since it allows for creating components with a
meaningful .json HTTP API for Communi...
hello,The Community Groups feature should always be used in the context
of a Community Site because of all the conventions and assumptions we
are making in this context (e.g. system user groups for controlling the
group roles & permissions). You can override the basepage template for
an entire Community Site as per the documentation here [0]. If you need
to override the presentation of a specific page within a site, then your
custom template can include this logic, maybe based on a property set ...
hello Alistaira simple option would be to overlay [0], specifically the
.scf-group-image classBertrand[0]
/libs/social/group/components/hbs/communitygroups/clientlibs/communitygroups.css
hello Alistair, it's a known issue and limitation, that activity streams
includes items that are entering a pre-moderation process. Please file a
support ticket if you need resolution in the short term - we haven't
seen pre-moderation being used that much lately. Bertrand
hello Greg, great questions/thoughts.SCD has been designed and tested
with much larger number of "members" (as we tend to name publish side
users). It's much more lighweight than before, and only uses the author
instance as a pivot (content is never stored as such on author). Also,
please note that compared to previous versions of AEM Communities, the
user node is quite lightweight also since we "moved" all the associated
UGC into SRP storage (activities, messages, notifications especially),
so ...
hello Nani, couple of options:1) you should look at our latest AEM
Livefyre technology:
http://www.adobe.com/marketing-cloud/enterprise-content-management/ugc-content-platform.html
- allows to curate content posted on Social Networks and expose the
feeds in AEM via the new Livefyre AEM components. 2) you can embed the
various widgets available on developer.facebook.com,
developer.twitter.com etc. into your AEM pagesBertrand
For this kind of pure-play "commenting and reviews" use case, you should
also look at AEM Livefyre technology - if you intend the build a broader
long term "community", then AEM Communities is a better fit
Can you please expand on why the "large number of users" cannot be
managed at the AEM level? The "enablement/learning" features of AEM
Communities could be a good fit for your project? There's also Adobe's
own LMS: Captivate Prime for pure-play LMS projects.
There are companies using the latest version of the product but we
cannot publicly advertise them as references at this point in a public
forum, sorry about that. The "reference" process can be tedious at times
- and with AEM Communities being a fairly recent product it takes some
times to do so
hello, although ASRP used to be tied to Adobe Social in the past, that
is not the case any more. ASRP now stands for "Adobe Storage Resource
Provider", and the moderation of UGC stored via ASRP also happens within
AEM now, including for the use cases you listed. Hope this helps.
hello NaveenWe do not have Polls planned at this point as a feature pack
for 6.1 or for the upcoming 6.2 release either. It is a roadmap item for
future releses of AEM CommunitiesBest regards
1) These topologies are equally valid for AEM Sites deployed along with
AEM Communities on the same instances, and on standalone deployments for
AEM Communities. 2) AEM Communities does indeed require a dedicated SKU.
In terms of persistence options - only ASRP requires an additional SKU
known as the "AEM Communities On Demand Extension", as it ends up
storing the Community content on hosted (by Adobe) servers. With MSRP,
you will have to run your own instances of MongoDB/SOLR. 3) Both MSRP
and ...
hello Marina,With the release of AEM 6.0, but also in the form of a
Feature Pack available to AEM 5.6.1 customers, we have a new generation
of Social Components (based on a new Social Component Framework) that
will give a much more interactive experience than the previous
generation, especially the "Comment" component that you would use on the
Blog template. If that is an option (e.g. if you are working with the
5.6.1 release), I suggest that you file a a support ticket so that we
can provide ac...
hello Marina,With the release of AEM 6.0, but also in the form of a
Feature Pack available to AEM 5.6.1 customers, we have a new generation
of Social Components (based on a new Social Component Framework) that
will give a much more interactive experience than the previous
generation, especially the "Comment" component that you would use on the
Blog template. If that is an option (e.g. if you are working with the
5.6.1 release), I suggest that you file a a support ticket so that we
can provide ac...
Hello Hari - we do not have prebuilt integration components for Lithium,
so you'll have to use the Resful APIs that Litihium provides for this
purpose [0].Also, please note that starting with Adobe Experience
Manager 6.1 (launch at Adobe Summit next week) we are releasing our own
community management platform [1], all built on AEM, so that AEM
customers in need of traditional web sites and community sites can run
both on the same platform, and of course get this kind of integration
natively.[0]
...
hi Chandra,For UGC support, you can also use the Cloud Storage (which
allows you to keep TarMK topology, with all instances, publish and
author, pointing at this "common store" for UGC in the cloud). This is
available for 5.6.1 and 6.0 versions (for 5.6.1, you need to download
and to install the Social Communities Feature Pack v1.4 from package
share). If you need to be provisioned for this cloud storage option,
please contact your Adobe representative.regards,Bertrand
