We have moved to GitHub Issues
You are viewing the read-only archive of Umbraco's issue tracker. To create new issues, please head over to GitHub Issues.
Make sure to read the blog posts announcing the move for more information.
Created by Ruben Shaw 05 Sep 2018, 01:03:19 Updated by Sebastiaan Janssen 06 Sep 2018, 14:02:29
As of current the scheduled ExpireDate (Unpublish date) is only exposed via IContent, meaning in order to display the ExpireDate on a page either the database needs to be hit on each request (ie using the content service to get an IContent to get the page's ExpireDate) or add a field to the doc type mirroring the ExpireDate value.
Neither of these solutions I believe are an acceptable alternative to having IPublishedContent expose ExpireDate.
There are valid reasons for needing to telegraph when a page will no longer be available, for example if a product is only available for a limited amount of time, transient pages, etc.
FYI: we're almost done completing the move to the new issue tracker as announced here: https://umbraco.com/blog/a-new-take-on-the-umbraco-issue-tracker/
I am closing the issue here on the old issue tracker, but it will continue on the new issue tracker. The new link is: https://github.com/umbraco/Umbraco-CMS/issues/2930 On GitHub, in the right-hand column, you'll find a "subscribe" button to be notified about updates to this issue.
Type: Feature (request)
Backwards Compatible: True
Affected versions: 7.12.1
Due in version: