bpang

I had to delete the plugin and reinstall after to get rid of the error, presumably since the version # did not change after the fix.

Same here. It can be resolved temporarily by installing the jQuery Migrate Helper. https://www.ads-software.com/plugins/enable-jquery-migrate-helper/

I have to say that I also tried all of the above solutions. The odd thing is the system has been running fine since the 5.3.2 release with no significant changes but the issue just started today. The issue even occurs despite the fact I have imagify resizing to 2000×2000.
– Upgrading to PHP 7.3 and then back down to 7.2 (I was on 7.2) did not fix it.
– Adding a filter to my child theme functions.php did not fix it.
– Removing imagemagick and finally doing a dpkg –purge on anything imagemagick related resolved the issue, though there were no resource constraints on it that I could observe.

I am thankful that it did not require a core downgrade, as I didn’t want to jump into that with multisite.

@lozula It could be another plugin triggered the cache wipe, perhaps autooptimize, a theme, or a social sharing plugin? You might want to check out this thread to try and narrow it down:
https://www.ads-software.com/support/topic/cache-keeps-getting-deleted/page/2/

I concur. I was the one who submitted the change to page specific as default in 1.3.2. I’m not sure why it was rolled back in 1.3.4 or what the rationale or use case is. I never want to clear the entire cache when updating just one post. For our blog, we update several posts per day which would cause the cache to be repeatedly cleared.

This is the commit I made:
https://github.com/keycdn/cache-enabler/commit/f8508ef3b1e0a2b3e39fd2d3daf32a7ff1233b50

I am just keeping my change in my local version of the plugin.

Yes, that “Page Specific” setting works fine. I actually submitted a pull request to change the default and I’ve changed the code locally on our systems. What I am at a loss to figure out is what periodically causes the entire cache to get wiped out. I had been using Auto Optimize and I’ve disabled that and the frequency of the cache wipes seems to have gone down, however it still occurs.

It does seem that the cache still gets periodically wiped out by something else, not quite sure what it is. :/

Ah, so as a quick fix, I just reversed the order of the array and submitted a pull request. https://github.com/keycdn/cache-enabler/pull/38

Thanks for your quick response @mohammed_kaludi
The fix works well!

It did the same to me. I rolled back to the previous version.

ArgumentCountError: Uncaught exception ‘ArgumentCountError’ with message ‘Too few arguments to function wptheme_nav_menu_item_id(), 3 passed in /home/username/wp/wp-includes/class-wp-hook.php on line 286 and exactly 4 expected’ in /home/username/wp/wp-content/themes/wptheme/include/function-regist.php:183

PHP 7.2.10

• This reply was modified 6 years, 5 months ago by bpang.

Getting the following error using PHP 5.5.8 / php-fpm:

2014/01/25 05:14:03 [error] 17589#0: *12574 FastCGI sent in stderr: “PHP message: PHP Fatal error: Call to undefined function mb_detect_encoding() in …/wp-content/plugins/follow-nofollow-control/simplehtmldom_1_5/simple_html_dom.php on line 988” while reading upstream.