tag:help-archives.hannonhill.com,2010-02-09:/discussions/general/20207-expiration-date-and-publishindex-under-system-tabCascade CMS: Discussion 2015-04-08T14:53:51Ztag:help-archives.hannonhill.com,2010-02-09:Comment/361744792015-03-02T16:00:53Z2015-03-02T16:00:53ZExpiration Date and Publish/Index under System Tab<div><p>Quick question about the expiration date on an asset: it seems
that when a page reaches its expiration date that the publish and
index options are unchecked under the "system" tab for the asset.
This makes sense, but what if the expiration date is reset to
further in the future? Is it required to manually check those back
on, even after resetting the expiration date? Right now that seems
to be the case, but I'm not sure if it's just because we have a
setting somewhere causing that.</p></div>Ashley Williamstag:help-archives.hannonhill.com,2010-02-09:Comment/361744792015-03-02T16:46:22Z2015-03-02T16:46:22ZExpiration Date and Publish/Index under System Tab<div><p>Hi Ashley,</p>
<blockquote>
<p>Is it required to manually check those back on, even after
resetting the expiration date?</p>
</blockquote>
<p>Yes, you'll need to manually check these options again if you
reset the End Date to some time in the future.</p>
<p>Let me know if you need anything else!</p>
<p>Thanks</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/361744792015-04-01T17:50:03Z2015-04-01T17:50:03ZExpiration Date and Publish/Index under System Tab<div><p>Sorry to come back to this so late, but are there any plans to
have the two options under System recheck if the end date date is
set to in the future?</p>
<p>We've trained our users to use the start/end dates for page
expiration, and adding in the extra step of checking those two
options in a separate tab isn't something they remember easily.</p></div>Ashley Williamstag:help-archives.hannonhill.com,2010-02-09:Comment/361744792015-04-02T18:49:14Z2015-04-02T18:49:14ZExpiration Date and Publish/Index under System Tab<div><p>No problem, Ashley. There aren't any plans right now to change
this functionality. I think part of the reason is because we don't
hear requests for this often (most of the time when assets expire,
they don't need to become 'live' again). When you have a moment,
I'd recommend filing an idea on our <a href="http://ideas.hannonhill.com/forums/52559-cascade-cms-ideas">Idea
Exchange</a> so that others may vote/comment on it. On that idea,
please also post your specific use case for needing to bring
expired assets back to a 'live' state.</p>
<p>Let me know if you have any additional questions.</p>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/361744792015-04-02T20:06:01Z2015-04-02T20:06:01ZExpiration Date and Publish/Index under System Tab<div><p>Ok! I'll definitely do that.</p>
<p>One more question: if an expiration folder isn't set for the
asset, will the expired asset unpublish if it's included in a
publish set that's set off at a later time?</p></div>Ashley Williamstag:help-archives.hannonhill.com,2010-02-09:Comment/361744792015-04-02T20:12:10Z2015-04-02T20:12:10ZExpiration Date and Publish/Index under System Tab<div><p>Great question. Expired assets will only un-publish if they are
being moved upon expiration. So, in your scenario, the expired
asset would still exist on the web server(s) even after the End
Date had been reached.</p>
<p>Having said that, if you don't actually want to move these
assets when they expire, I believe you can simply set the
expiration folder to be the current parent folder of the asset.
Then, when the End Date is reached, the asset will be moved but
will end up in the same location (and the 'move' should trigger the
un-publish).</p>
<p>Let me know if this helps!</p></div>Tim