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

How can we restore a deleted page within a touch UI ( not using WCM, classic UI)? Does AEM have a concept of "Trash" can?

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.

Yes, we have opened a ticket on it (BTW, we also have some issues with launch feature). Thanks again for your replies.

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