Plugin Support
Dake
(@dakeg)
Hi @sahro & @sabababenji
Thank you for sharing this with us. I have informed our developers and we will get back to you as soon as we have any information about this notice.
Plugin Support
Dake
(@dakeg)
Hi @sahro & @sabababenji
Just to confirm, have you already tried temporarily disabling WP Mail SMTP to confirm if the notice disappears and reappears only when WP Mail SMTP is active?
Also, where exactly does the notice appear?
Have you also tried disabling your other plugins except for WP Mail SMTP and W3 Total Cache to confirm if the error continues to appear?
Thread Starter
sahro
(@sahro)
WP Mail SMTP 3.8.0 + W3 Total Cache -> problem
WP Mail SMTP 3.7.0 + W3 Total Cache -> no problem
WP Mail SMTP 3.8.0 without W3 Total Cache -> no problem
W3 Total Cache without WP Mail SMTP -> no problem
Plugin Support
Dake
(@dakeg)
Hi @sahro
We are still attempting to reproduce this issue on our end.
As mentioned in my previous response, where exactly does the notice appear? Does it appear throughout the admin dashboard? Does it appear only in W3 Total Cache settings etc?
Please try re-installing both the W3 Total Cache and WP Mail SMTP plugins.
Also, can you and @sabababenji share your currently active plugins so we can check to see if there are any shared plugins that may be contributing to this issue?
Are you seeing any errors in the Tools>Site Health section?
Lastly, does the error appear each time you attempt to purge all cache?
Thread Starter
sahro
(@sahro)
So I did the following:
1- I uninstalled all plugins except: WP Mail SMTP 3.8.0 and W3 Total Cache -> same problem
2- I reinstalled the two plugins and I changed the theme to a wordpress theme -> same problem
Plugin Support
Dake
(@dakeg)
Hi @sahro
Thank you for keeping us posted. We are still not able to reproduce the issue on our end, we have tested this by enabling:
- Page cache
- DB cache
- Object cache
And after clearing all cache, no errors are reported.
It would be quite a coincidence, but perhaps you and @sabababenji are using specific configurations that are causing the error to trigger. Please share a screenshot of your current W3 Total Cache settings should, so we can test it out. Also, have you already reached out to the W3 Total Cache team in case they can shed some light on the situation?
Lastly, which PHP and WP versions are you using?
Thread Starter
sahro
(@sahro)
Plugin Support
Dake
(@dakeg)
Hi @sahro
Thank you for sharing screenshots, we are still looking into this and are attempting to reproduce the issue.
We will get back to you as soon as we have any updates.
Plugin Support
Dake
(@dakeg)
Hi @sahro
We copied your W3 total cache settings, but we were still not able to reproduce the issue.
As a quick test could you temporarily disable the minify feature and then clear your cache to see if the error remains?
Also, have you reached out to W3 Total Cache Support team to confirm if anyone else has shared this error with them?
Thread Starter
sahro
(@sahro)
When I disabled “Object Cache” the error disappeared.
no I did not contact the W3 Total Cache support team.
Plugin Support
Dake
(@dakeg)
Hi @sahro
Thank you for getting back to us.
Does the error re-appear once you re-enable Object Cache?
Thread Starter
sahro
(@sahro)
Yes, the error reappears once I re-enable the object cache.
Plugin Support
Dake
(@dakeg)
Hi @sahro
Thank you for confirming, I have shared this with our developers.
Once again, we’ll get back to you as soon as we have any updates.
Plugin Support
Dake
(@dakeg)
Hi @sahro & @sabababenji
Thank you for your patience.
We were able to confirm that this is a known issue on W3 Total Cache’s end. They had created a GitHub issue regarding this issue on Nov 17, 2022 (https://github.com/BoldGrid/w3-total-cache/issues/584).
To get technical, they need to implement wp_cache_flush_runtime function in their plugin. The notice is appearing in our settings because the Action Scheduler library uses the wp_cache_flush_runtime function.
It’s a WP core function, but it’s included only if the external object cache is not enabled. Since W3 Total Cache enable external object caching, they need to implement the aforementioned function on their own (like they implement other functions from object cache API).
