24-06-2021
- Mark as New
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Thanks for the link. Having worked with AEM (and CQ before that) we understand how it works.
Specifically, because of the auto-unpublish, using the OOTB expires functionality is almost useless for both us (Accenture internal AEM implementation and our clients. In working with AEM for the last 8 years, I have never had a client that was able to live with having pages break when an image expires. For clients that want to use rights management capabilities, we've had to implement a custom expiration solution because we can't just have pages break when an image expires and then have to go back and fix them. All we're asking for is the ability control whether to unpublish images automatically or not based on some configuration (e.g. auto-unpublish = on/off) would solve for this. While we understand the risk of unlicensed content, we have to balance that against the poor experience and brand reputation of broken images on web pages.
We currently have to implement a custom expiration field, create a custom search predicate to look ahead to assets about to expire, and implementing all the other "expires" functionality such as making it so a user without administrator permissions cannot edit, copy, move, publish, and download an expired asset for our custom field.