Hey @Nupur_Jain , Thanks for the thorough analysis, I see the issue with
the Launch promotion as you mentioned. Do we agree that this is a defect
in AEM or is it an intended behavior or system configuration?
Hey @Nupur_Jain, The project is configured to auotmatically promote
Translation Lanuches and approve them. I check the list just in case and
the pages are not there. I have tested to update text in some components
within the page and that is being updated it is only the page properties
that do not get updated. In our case it is the page description. The
page description gets translated if I am created a translation for a new
language and the language copy it is created for the first time. If I
h...
Hi @Nupur_Jain ,I have updated the questions, sorry there are no live
copies involved here it is a matter of language copies translated from
english. Steps: - Update page x properties (Description)- Mark the page
in sites and open Reference side menu -> Language Copies- Choose the
language copy from the list of existing language copies and click Update
Language copies - Select Project and click Update (I select use Existing
project and use the one I have already).- I run the Translation Job in
t...
We have language copies of a site, all language copies are translated
based on the english master site. Translation works fine when running
for a new language copy, but once updating page properties ex. page
description (jcr:description) the new text is not being
translated/reflected on the existing language copy. The description is
being translated the first time as this property is defined in the
translation_rules.xml, so this is failing only when updating an already
existing language copy. We...
Thanks for the answer Arun, yes we ended up looking into experience
fragments and utilising. It was not that obvious as there are no
documentation (at least nothing we found) about this. However, it seem
that Adobe implemented the functionality sepcifically for
core.wcm.components as an extension to the standard XFcomponents. This
require then that we strictly follow the recommeded site structure for
MSM (BluePrint vs live copies) and reflect that into the Experience
Fragments setup.
It seem to me the Editable Templates are useful for a single site usage
as design/policies configurations are defined on template level. i.e.
imagine to identical sites in structure but they have different
design/policies configurations for structural components (ex. header,
footer), then in this case you will need to create to set of identical
editable templates to be able to define different policies for the
structural components on those sites, which does not seem like a
beautiful solution to...
We have similar situation right now and I am looking into a solution for
the above. it seem to me the design/policies are defined on template
level and hence same template cannot be used on two different site with
different design configuration. So solution I see is to create a set of
templates per site which would result with big amount of templates. Did
you find a solution for above, or did you end using static templates?
I am trying to get the TagCloud onto the ContextHub to simulate the data
for the different standard users provided with AEM 6.3 quick-start. The
tutorial provided was pretty simple and I have added the module for
tagcloud as per instructions.Once the ContextHub is loading in the page
the TagCloud is failing to load and a JS-error appears in the console
see imagesIs this a mistake in my configuration, tutorial or a bug?
Appreciate all help
