@Mario248 It is still at instance level. You can try
if it fixed groups and add users manually at instance level and to
enable them in publisher just replicate the groups and users.
@AEMUSER1000 If i understood your problem stmt correctly, you have set
of pages/assets in a your system. You are trying to update them as bulk
using a content package, when you upload/install the package in author
and replicate the package, dispatcher cache for those individual
pages/assets is not getting flushed? while if you do publish individual
pages/assets your dispatcher cache is getting flushed? If above is your
problem stmt, please configure
@arChieZ As far as i know there will not be any difference from AEM
Integration perspective if it is Solr6 or Solr 9. Only the differences
will be in using the latest feature in Solr9 while running your queries
from your client application and it is always backward compatible.
@VinayHegde It depends on the complexity of the business logic and
frequency of date to be updated in that xml. If it is too heavy
execution and content is not too dynamic, i would prefer to run the
logic offline maybe as scheduler once in a day and store the xml as
physical asset in DAM path and i would point my dispatcher/rewrite rules
to point to DAM location based on the public url you want to have. If
the content is dynamic in nature changes as and when requested, say
price related etc.. no...
@getaylormerkle can you please cross verify your configuration as per
We followed this and everything is working as expected. Maybe
storeid/catalogid missing or somewhere.
@Itsmevink can you please provide more details like, what are properties
names for which translation not working, screenshot from crxde and how
are we translating them? Any live copy, language copy involved? Are you
getting any launches in between I'm translation projects?
Yes for Livecopy rollouts, we have MSM Rollout configurations available
via OSGI..but for language copy updates which will get updated by
creating launch copies and promoting them after, if jcr.* properties got
updated in launch copies such as page titles, desc or alias fields and
when we promote launches, updated content is not reflecting in Language
copies as these are excluded under
"/libs/msm/launches/rolloutconfigs/launch/contentUpdate".. Question here
is, how do we update a property for a ...