On 2011-03-31, at 8:44 AM, Zdravko Balorda wrote: > Phillip Smith wrote:
>> If the story has an expire date in the past, the template never runs, so I'm not sure what you're proposing...?
> Not for the past. If story has an expire date in the future, when it's removed
> from the site by the expire job, the link to this now non-existing story still
> exists on corresponding cover pages.
I see what you're proposing. You're proposing to create a republish job in the future for the cover story that would happen after the linked story expired. I guess that would work for stories that had expire dates far out in the future. However, many people _expire_ a story in a hurry -- e.g., something they want to remove from the site -- and, when they set the expire date, and republish it, it does not re-run the template, thus no republish job would be created. > I'am not sure what to do with expire date in the past!? Why would you need to
> run the template?
Because I have stories that write themselves to an external database and I want to remove them from the database if/when they are expired. Thus, to do that in "real time," I need to re-run the template, check if the story is expiring, and remove it from the database. Right now, I have to use a cron job to check for expired stories.
Phillip Smith http://phillipadsmith.com http://twitter.com/phillipadsmith http://linkedin.com/in/phillipadsmith