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
It's meant to happen automatically with a background scheduled task.
Maybe you can setup a logger for
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.
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
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
hi Sandeep,You need to use the SCF/SRP APIs to query Community content
(query builder won't
plenty of samples on GitHub, e.g.