How this "resources" sub folder works with any 3rd party library which
contains images? do we have to modify 3rd party library code to change
image path references? we need a better way to handle this.
How do you define the policy for the component has parsys container but
this component is put on page multiple times? the policy works only for
the first one you put on the page but not work for the ones after since
the content node it generated is component name + a random #. For
example below, 'apps/custom/components/my-component' component has a
parsys container: - my-page -- jcr:content --- root ---- my-component (
resourceType: apps/custom/components/my-component) ----
my-component_12312312...
we have the similar issue with 6.5. we have one component has a parsys
container and this component is put on a page multiple times. The policy
only worked for the first one but not work for other same component. It
seems that policy mapping is based on node path not by component
resource type.
Thanks for the quick response. Yes, we knew we can restore a page to
previous versions. Restoring a deleted page is pretty different; do you
know when Adobe will add this functionality? thanks.
Thanks for the quick response. I checked the
"/content/we-retail/language-masters/en/jcr:content", it doesn't have
the jcr:language property. Looks like you are very knowledgeable, can
you give us the clear instruction on this? thanks.
Try the following steps with out of box setup & We.retail application
with default MS translation engine (6.4 + SP2):From
"/content/we-retail/language-master/en", pick couple of pages to do
language copy to ther language sites, e.g. FR & DE. Note that, you have
two ways to create language copy: a). from AEM console, use "create"
dropdown menu; b) from reference panel, use "References" and then
"language copy" Follow through the widget, for translation project
selection, please choose "create a m...
Hello,We are experiencing a serious issue with project functioanlity
related to translation after upgrading to AEM 6.4. The "creating
project" and "Adding to existing project" from reference panel in touch
UI behaviors inconsistently in AEM 6.4, even with out of box we.retail
application. The issue is that after language copy from a "us" site to
another language sites (e.g., French, German) by creating a
multi-language project. After that ( page translated and come back), you
cannot reuse existi...
With 6.3 SP1, the scheduled Activation still doesn't work with
publishing multiple pages together and pages have different version #.
Still a big issue for us.
Anil, have you gotten any reply on your questions? we also found that
the OOTB content approval workflow is so difficult use and spent lots of
time to customize it. To us the requirement is very simple: for each
step we can specify who/which group can review and approve or reject the
content; and the notification can be done through email notification;
the workflow step message can be specified clearly what's the content
and what reviewer needs to do. Unfortunately, AEM doesn't provide this
kind...
Thanks for your quick response; appreciate it!This feature hasn't worked
since earlier version; I have to ask: why the functionality is made
available to users when there are issues and not working? can you tell:
is AEM still developed/maintained by day software developers?Thanks.
Hi folks, We are also looking at this functionality since we started
using AEM 6.1; it just didn't work!!! Now we are trying to use it in AEM
6.3 and it has lots of issues and the functionality is not stable. You
can access the version compare ( compare an old version with the current
page copy) functionality from touch UI console: select a page, expand
the timeline from left rail and select a version, then it will allow you
to compare that version with the latest editing copy. This feature is
i...
