When publishing a new Property (CPT) there is still a delay of up to several hours, which I assume is the GoDaddy Managed WordPress caching mu plugins in effect.
However, when publishing a normal blog post, the post appears immediately. So the cache is ONLY affecting the Views content.
When the cache is flushed (GD Managed WP provides a "Flush Cache" button) the Views content appears immediately.
The client does not want to have to click the Flush Cache button each time - is there ANY other way to prevent Views from being cached??
The debug info I provided is for a staging version of the site that's identical to the production site. I've replicated the exact same issue on both. I can provide full access to the staging site if needed.
Hello. Thank you for contacting the Toolset support.
First of all, I checked the debug information you shared with us and I found that you are using outdated views plugin. The latest views plugin version is 2.3.1. You can download it from:
=> https://toolset.com/account/downloads/
Regarding cache issue - this issue is really related to your hosting provider GoDaddy and its popular one. I found one help page which will guide you to bypass the managed WP cache:
=> hidden link
Views has been updated, thanks for pointing that out!
I was afraid this would be your answer. I understand the GoDaddy Managed WordPress caching is difficult to deal with.
But do you happen to know - or can you provide documentation for - the reason why normal WordPress Posts are not cached in this manner (they appear immediately when Published) but Views CPTs are cached?
What is the difference between normal posts and Views CPT output if we are telling Views to bypass the cache?
Is there ANY way to write a function that tells WordPress to treat a CPT the same a default Post? (I know that's an oversimplified question for a complex issue).
At the end of the day, I understand the issue itself is with GoDaddy's cache - but I very greatly appreciate any additional insight you guys can provide on this issue.
What is the difference between normal posts and Views CPT output if we are telling Views to bypass the cache?
===>
Views offer the way to bypass the cache and you already tried that by adding the attribute to views shortcode cached="off" but the thing is that what if your hosting authority prevents the view's query.
Is there ANY way to write a function that tells WordPress to treat a CPT the same a default Post? (I know that's an oversimplified question for a complex issue).
===>
We would like to help you but the thing is that how can we control GoDaddy caching. We simply can not control it.
