equin0x80

I managed to turn it off with this SQL command on the database:

update wp_n9qwinoptions set option_value=’no’ where option_name = ‘woocommerce_calc_taxes’

It seems to have worked. But there’s still the question of why the tick box doesn’t work, and I am concerned that it might turn itself back on if we change other settings in future! Thanks for any info.

I just saw the exact same error during upgrade, but only one of two WordPress installations. Here are more details about my case:

* I have a test site (“site A”) that has been under development for a while, on my own server.
* I recently copied this entire site to another host and domain, in preparation for go-live. Call that copy “site B”. I fixed it up manually by changing the config files and doing search-and-replace on links in the database. (I’m new to WordPress so it’s possible I missed something here — but everything seems to work fine.)
* When I logged in to site B’s dashboard, it said Jetpack was in Safe Mode due to detecting a duplicate site (fine): I chose “Fix Jetpack’s Connection”, since site B is the new primary version that will some day be a live site.
* I then upgraded site B, which indicated success but also displayed the exact error shown in this thread.
* I then went back and logged into site A, got the same Jetpack Safe Mode message and this time chose to stay in safe mode (since site A is my old testing copy).
* I updated site A and did *not* see any error.

So I wonder if this error might relate to (i) Jetpack Safe Mode, or (ii) WordPress installations that have been created by copying an existing install and manually fixing things.