No, not at the moment and this is not planned.
It can be done, but would require a mapping input field group which would only make things much, much more complicated.
To turn off the cache on some pages there is a new function in the yet-to-be-released git version already.
Thread Starter
xberg
(@xberg)
Thanks for your answer.
I was thinking about the homepage. New articles get posted there several times a day. I would not want to completely disable the cache as this is the most visited page but I would certainly not be happy with a 24-hour cache for this page.
But I understand your concerns about complexity.
What if you set cache invalidation to “modified post and posts index page”?
Thread Starter
xberg
(@xberg)
I do not have this option in my settings 🙂
I have:
– flush cache
– modified post (this is what I am using)
– modified post and all taxonomies.
Thread Starter
xberg
(@xberg)
Is there a way I could just purge the homepage from the cache?
I tried the empty cache button but its effects are extreme as it even empties the object cache contained in memcache.
I also tried setting to modified post and all taxonomies but that does not reset my homepage on a new article publication or modification.
> I tried the empty cache button but its effects are extreme as it even empties the object cache contained in memcache.
You can use a different memcached as backend for wp-ffpc to prevent this.
—
I’ll try to add the frontpage to the post & taxonomies option.
—
I would highly recommend to set a low time on the cache for now, like 100s; in this case, there will be only a slight delay in showing the new version of the frontpage and a single boost of visits will not trigger any issues on a sub-page either.
