Page wrongly displayed when cache plugin activated
Page wrongly displayed when cache plugin activated
Page wrongly displayed when cache plugin activated
Using the Network tool in the Inspector I found out that there was a third party caching service in action. “Cloudflare” via Bluehost.
Last time I used this plugin, you had to flush the entire cache to do this: add_action(‘save_post’,’custom_clear_wp_super_cache’); function custom_clear_wp_super_cache($post_id) { if (function_exists(‘wp_cache_clear_cache’)) {wp_cache_clear_cache();} } There may (or may not) be a method of flushing the cache for a particular post now.
Were you using any cache plugins like W3 Total Cache? If so, you’ll need to get access via sftp or ssh to disable the plugin (rename the dir wp-content/plugins/w3-total-cache to something else).
try edit wp-config.php and see if there is any WP_CACHE defined , if so remove . you may also see caching setup file link , if so you should remove that too . now open your site and please hard reload your page by pressing control + f5 (on windows ) or shift + refresh … Read more
Honestly, if you don’t understand what is meant by the query string and you’re not a developer, then Standard will be fine. It’s the safest option without knowing more about your setup—choosing Ignore Query String could break your WordPress site depending on how it’s set up.
Caching is not magic, someone needs to write the code for it. Caching plugins will handle most basic page types in wordpress, but anything which is not a post will most likely need to have an explicit integration with the caching plugin, or just have its own caching. side note: it is a big no-no … Read more
If this is on a specific page you’ll be able to exclude the page from being cached under Performance > Page Cache > Advanced. If it’s on every page you’ll have to enable fragment caching. Set the method to Disk: Basic and enable Late Initialization in Performance > Page Cache > Advanced. Set the following … Read more
Indeed, you have to be careful when using __destruct. This is a special function that fires when the object is about to be destroyed. When PHP calls exit (as wp_send_json() does), we do not control in what order PHP will destroy the objects. So __destruct is very dangerous when it relies on other classes. I’ve … Read more
Sounds like you are looking at it from a very low layer POV. fetch_feed provides caching so you will not need to wait for a response on possibly every page load. Therefor, as long as there is a cache you are unlikely to even want a message to be sent and obviously you are not … Read more