NN777 VIP.Claim Your Free 999 Pesos Bonus Today

Resolved

(@sean-h)

Weird problem. Every now and again, after updating or publishing a post, when trying to leave by clicking on the WP logo top left, I get a critical error, and an email with the error log. At least the post is successfully saved, yet this supposed critical error keeps popping up sporadically.

Funny thing is a simple page refresh and all is well, but this has happened 3 times this week, so I have to wonder what’s going on. Siteground are also not sure what the problem is, even though the error is pointing fingers straight at the SG Optimizer plugin.

I’m going to post the whole error, it’s not that long, but if you look carefully, there is also a reference to WP Recipe Maker, which is why I thought to post it here.

Also, every time we save a recipe card, it says ‘this is taking a long time’ at the bottom of the card, but it always saves anyway, never takes longer than 3-4 seconds (I must actually count next time). So, I have to wonder if this has anything to do with the sporadic errors I’ve been getting?

Any ideas?

WordPress version 6.3
Active theme: Divi (version 4.22.1)
Current plugin: SiteGround Optimizer (version 7.4.0)
PHP version 8.1.22

Error Details
=============
An error of type E_ERROR was caused in line 503 of the file /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/sg-cachepress/core/File_Cacher/File_Cacher.php. Error message: Uncaught TypeError: array_diff(): Argument #1 ($array) must be of type array, bool given in /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/sg-cachepress/core/File_Cacher/File_Cacher.php:503
Stack trace:
#0 /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/sg-cachepress/core/File_Cacher/File_Cacher.php(503): array_diff(false, Array)
#1 /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher.php(213): SiteGround_Optimizer\File_Cacher\File_Cacher::purge_cache_request('https://www.the...', true)
#2 /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher.php(197): SiteGround_Optimizer\Supercacher\Supercacher::purge_cache_request('https://www.the...')
#3 /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher_Posts.php(221): SiteGround_Optimizer\Supercacher\Supercacher->purge_rest_cache()
#4 /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/sg-cachepress/core/Supercacher/Supercacher_Posts.php(152): SiteGround_Optimizer\Supercacher\Supercacher_Posts->is_post_excluded_from_cache_purge(Object(WP_Post))
#5 /home/customer/www/thetastychilli.com/public_html/wp-includes/class-wp-hook.php(312): SiteGround_Optimizer\Supercacher\Supercacher_Posts->purge_all_post_cache(18226)
#6 /home/customer/www/thetastychilli.com/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(NULL, Array)
#7 /home/customer/www/thetastychilli.com/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#8 /home/customer/www/thetastychilli.com/public_html/wp-includes/post.php(4751): do_action('save_post', 18226, Object(WP_Post), true)
#9 /home/customer/www/thetastychilli.com/public_html/wp-includes/post.php(4853): wp_insert_post(Array, false, true)
#10 /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/wp-recipe-maker/includes/public/class-wprm-recipe-saver.php(400): wp_update_post(Array)
#11 /home/customer/www/thetastychilli.com/public_html/wp-content/plugins/wp-recipe-maker/includes/public/class-wprm-recipe-saver.php(326): WPRM_Recipe_Saver::update_recipes_in_post(18229, Array)
#12 /home/customer/www/thetastychilli.com/public_html/wp-includes/class-wp-hook.php(310): WPRM_Recipe_Saver::update_recipes_check('')
#13 /home/customer/www/thetastychilli.com/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(NULL, Array)
#14 /home/customer/www/thetastychilli.com/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#15 /home/customer/www/thetastychilli.com/public_html/wp-admin/admin.php(175): do_action('admin_init')
#16 /home/customer/www/thetastychilli.com/public_html/wp-admin/edit.php(10): require_once('/home/customer/...')
#17 {main}
 thrown

This topic was modified 1 year, 7 months ago by Sean.

The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)

Plugin Author Brecht
(@brechtvds)

1 year, 7 months ago

Hi Sean,

The error does seem to be originating in the SG Optimizer plugin, so I would expect them to be able to debug that.

The reference to WPRM seems to be there because we are triggering a wp_update_post, which is a default WordPress function.

Is the other problem related to the SG Optimizer plugin as well? Does it save faster when that plugin is deactivated for a second?

Thread Starter Sean
(@sean-h)

1 year, 7 months ago

Hi Brecht,

Yes, Siteground have since admitted the error is most likely caused by the SG Optimizer plugin, only they are still not sure how/or why it is happening. Apparently something to do with scandir() not finding the file it was looking for when clearing/pre-heating their file based caching system. I was just curious though why WP Recipe Maker is mentioned in the email sent by my site. Hence this post.

But about the other small issue. Small, in that the card always saves anyway. I first experienced it when I tried Siteground’s new in-house CDN. When I stopped with the CDN trial, the recipe card ‘taking a long time’ issue went away. Now we are using their premium CDN once again, a newer version, and it is working very well, only the ‘taking a long time’ issue is back on the recipe card. But again, it saves anyway. I just checked; Siteground CDN off, but the SG Optimizer plugin still on full, card saves quick. CDN on, card ‘takes a long time’, about 2-3 seconds longer.

Now why I find this 2nd ‘issue’ very weird is I thought as a logged in WP admin user I have bypassed the CDN. Which is why I find it odd that saving the recipe card appears to be affected by the CDN.

But in both cases, everything is actually working quite fine. These are more just annoyances than anything else, until it outright breaks.

Anyway, if you have time and come up with any more idea, I’m all ears.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Fatal error’ is closed to new replies.