I create an Article content fragment model.I create a few Article
content fragments with tags for each one.I create new Article pages and
drop these Article content fragment into them.I create a new page and
put the Core List component on it. I configure it to look for a specific
set of tags under the /content directory. The Core List component will
look for tags from the pages, but it does not look for the tags from the
content fragment. Is there a way to configure or extend the Core List
Can you elaborate on this ?Can you give an example on what you mean ?
One thing I have noticed is that after a package is deployed, sometime
not all the bundles are in active state. I believe it's because we are
install the next package before all the bundles are active.A lot of our
time is spent on the verification step since we are not confident the
code package is deployed properly to all AEM publish instance. I'm
trying to see how other are solving this problem.
Our current deploy to Production takes around 3 hours, I would like to
get some feedback on how we can improve this to reduce it to less than 1
hour.We have 16 AEM publish instances in 2 data centers. We install AEM
packages using http requests. We use Akamai to cache the static pages.
Here are the steps to our deploymentRoute all traffic to DC1 (data
center 1).Deploy AEM packages to publish instances (8). Deployment is
done all at once. We have multiple code packages.Restart all AEM publish
What version of we.retail are you using to have the content fragment
component show the multiple elements field ? I looked at the latest
we.retail version 4.0, and the
you be more specific on your setup to make this work ?