W3 Total Cache, Advanced Custom Fields (ACF) and Page Cache
-
Hey ho,
at first we want to thank Frederick Townes for developing such a great plugin, which allows WordPress to deal with a large amount of posts and content, without loosing page visitors because of bad page speed.
Nonethethess we experience a bad behaviour if the content gets to complex. For better content structure and flexibility for our authors, we use ACF (https://www.advancedcustomfields.com/). If a user changes content on a post (in an ACF-Field) the plugin works well and flushes the cache of the post. The changes, which has been made, are published and everything is fine.
To enhance the experience for the authors with WordPress and decrease the time of updating content, sometimes some content modules like teasers, sliders, lists ( ACF-Fields like Repeaters or Flexible Content) or whatever consist of content from other pages/posts/customposts. If changes are made on the original post, the modules on other pages/posts still show the old content.
Is there a way to force W3TotalCache to clean the cache of the posts, where content is “included” via ACF from other posts? I think this has to be done in the template because W3TotalCache can’t really know where exactly and in which post, content is “included” from other posts via ACF.
Our Plugin Settings aren’t really special. PageCache on, Object Cache on and DB Cache on. No Browser Cache or Minify.
Thanks in advance.
David
- The topic ‘W3 Total Cache, Advanced Custom Fields (ACF) and Page Cache’ is closed to new replies.