Cache invalidation for future dated (pending) elements

[angrybrad]

Created by: Timothy Kelty ([email protected]) on 2015/04/02 12:33:05 +0000
Votes at time of UserVoice import: 6

---

Wherever I'm using the cache tag, I find myself eventually having to use this solution, if a client tries to use future-dated entries: http://craftcms.stackexchange.com/questions/2610/how-can-i-cache-a-list-of-entries-with-pending-postdates-and-have-it-automatical

Seems like there should be a way to bake this into Craft's native cache invalidation routines so I didn't have to do the same thing on every template.

[MoritzLost]

I just came across this issue in a project, +1 for the suggestion to handle this natively. Would be great if Craft could handle this scenario, even though I'm not sure how this could be solved.

Another related issue: What about creating new entries that would match an element query inside a cache tag? For example, let's say I have a calendar page that lists entries chronologically and I'm caching the entire entry list. Saving any entry in that list will invalidate the cache. But adding a new one that should be displayed in that list will not.

Again, not sure if there is a good solution to this issue. Maybe keep track of the element query somehow and execute it after every save to see if the results changed? Though maybe that's too complicated.

How are y'all handling those issues right now? Especially in scenarios with a lot of nested component templates, where the {% cache %} tag isn't necessarily aware of the element queries that are going to be executed inside of it (like the linked answer assumes)?

[brandonkelly]

We are moving support for future entry publishing/expiring to scheduled jobs in Craft 5, which will resolve this (see #8847). In the meantime, this module can be used to accomplish it.

[MoritzLost]

That's great, thanks @brandonkelly! Looking forward to this in Craft 5. In the meantime I'll have a look at that plugin.

[mikesnoeren]

We are moving support for future entry publishing/expiring to scheduled jobs in Craft 5

I couldn’t find any documentation on this. Has this feature been released, or is it still planned for release?

[MoritzLost]

@brandonkelly I was also looking for a solution on this – is something like this already implemented, or planned?

[FreekVR]

This problem affects headless sites heavily.

Because the GraphQL cache isn't invalidated when a scheduled post should appear, the post in question will never show up until something else in the CMS changes.