Conflict with redis cache plugin

That shouldn’t happen on every single flush. There are three places where the code calls wp_cache_flush

1. On init IF the DB version is out of sync – https://plugins.trac.www.ads-software.com/browser/varnish-http-purge/trunk/varnish-http-purge.php#L145

2. When upgrader_process_complete runs – https://plugins.trac.www.ads-software.com/browser/varnish-http-purge/trunk/varnish-http-purge.php#L209

3. On the purge command IF you’re passing “object” as a type to flush (which is only set when you pick the ‘flush object cache’ from the menu) – https://plugins.trac.www.ads-software.com/browser/varnish-http-purge/trunk/varnish-http-purge.php#L587

I would try commenting out that 3rd section, but there’s no logical way that should be running on every post unless one of your writers is also force flushing the whole cache, or you have another plugin that’s hooking in to this plugin.

I’ve been testing here.

1) db version is the same as in “version.php” file which is 48748

2) Not running any upgrade process every minute, but I have a plugin called stream which I use for monitor network actions such as deletions and posts edits, I found that when “proxy cache purge” was active the plugin “stream” was recording a lot of these records: “Stream Database Version” setting was updated: https://i.imgur.com/hA6sYnI.png

3) Not running flush from admin menu

Made a search in my project and these are the plugins that are calling wp_cache_flush: https://i.imgur.com/n6bLK7k.png

Also tested updating a post in my dev env and flushdb isn’t called.

• This reply was modified 4 years, 5 months ago by edemir206.
• This reply was modified 4 years, 5 months ago by edemir206.