Hello, Can we talk about this again? Akamai has improved their system and cache can be purged within seconds by their API or console app. This has made the AEM integration with Akamai on cache purging more meaningful. Akamai should be configured to cache content with a long time period to improve page loading performance. AEM/Akamai is a such common setup for most of Adobe customers, I wonder why Adobe cannot have an out of box service component doing the integration.

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. 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...

We have the same issue and a simple "folder" functionality will make UX much friendly for organizing activities and audiences.

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...