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 pa...
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, 'a...
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.
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 t...