Update 4.6.0 causes fatal server error

Thanks Rogier for your support.

I think I’ll wait for the update, since I’ve looked into the server log again and it seems the error didn’t occur after rolling back CAOS to version 4.5.0 this afternoon. So I won’t be able to tell if the fix would be working or not.

Might it be a conflict with latest CAOS version (4.6.1) only?

Anyway, you’re right about opening a thread in the Complianz forum, but apparently I didn’t know that it was a lack of your plugin, since I don’t have the skills to translate those server errors… I just assumed it would be linked to the updating error! ??

Cheers!

I changed/improved the way settings are retrieved from the database in 4.6.0. That’s where the conflict with Complianz was coming from. I spoke to Rogier, they’ll update it soon. But it’s a warning, so there’s nothing to worry about. It won’t crash your site.

I’ve been able to reproduce the error during update, and I can confirm that it was related to the do_update_after_update function.

The only thing I can’t quite understand is that there apparently is a moment where the new code executes in class-cron.php, but runs into the old code in class-caos.php.

Maybe the upgrader_process_complete action is triggered too soon, or PHP caches (like Opcache, Varnish or Cloudflare APO) are in the middle of flushing after the update at that point?

To be honest, I don’t know. What I do know, is that after 4.6.1 this error won’t come back and the update process does actually succeed, although WordPress says it doesn’t.

Also, it won’t crash your site, because it only occurs during the update process of CAOS to 4.6.1. After that, it won’t happen again because do_update_after_update is removed.

Hi Daan

Here is the full log. This was sent via the “Your site is experiencing an issue” wordpress email.

Error Details
============
=
An error of type E_ERROR was caused in line 165 of the file /home/mysite/public_html/wp-content/plugins/host-analyticsjs-local/includes/class-cron.php. Error message: Uncaught Error: Call to undefined method CAOS::get() in /home/mysite/public_html/wp-content/plugins/host-analyticsjs-local/includes/class-cron.php:165Stack trace:
#0 /home/mysite/public_html/wp-content/plugins/host-analyticsjs-local/includes/class-cron.php(38): CAOS_Cron->build_download_queue(
)
#1 /home/mysite/public_html/wp-content/plugins/host-analyticsjs-local/includes/class-caos.php(293): CAOS_Cron->__construct()
#2 /home/mysite/public_html/wp-content/plugins/host-analyticsjs-local/includes/class-caos.php(349): CAOS->trigger_cron_script()
#3 /home/mysite/public_html/wp-includes/class-wp-hook.php(308): CAOS->do_update_after_update(Object(Plugin_Upgrader), Array)
#4 /home/mysite/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#5 /home/mysite/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#6 /home/mysite/public_html/wp-admin/includes/class-plugin-upgrader.php(371): do_action('upgrader_proces...', Object(Plugin_Upgrader), Array)
#7 /home

Hi.

Adding: define(‘CAOS_OPT_CACHE_DIR’, ”); in wp-config, it works!

With versione CAOS Versione 4.6.1 Error is still present.

I have Complianz v 6.4.7

Thanks!

Ciao
Davide from Italy in a sunny day.

Hi guys,

Please refer to my latest response to this thread.

Yesterday I replicated the issue on a testing machine, and using a fictional future update (4.7.0) I can confirm that the fatal error will no longer occur after 4.6.1. Unfortunately there’s nothing I can do about any release before that — I can’t change the code already present on your servers. ??

Thanks for your help and cooperation!

Alright Daan,
so let’s update to 4.6.1 and that’s it until next release?
I confirm that beside the update process being interrupted by that error, the site apparently continue working (despite that single server error on update). I don’t know why the first time (only) I had to go through Recovery Mode.

Good to know about the Complianz fix as well, so let’s move on and wait for the updates without worries.

Thanks for your support, really appreciate it!

Best,
Marco

Yes, the error won’t occur again after 4.6.1. Wish I found this earlier, but it is what it is.

No problem! Have a great weekend!

Thanks for clarifying!

And have a great weekend you too!