2.3.5 update caused critical error

And this happened with WP 5.6.2 and WC 4.9.0. I haven?t tried again with WP 5.7, nor WC 5.1

This is because they checked for a class existing and then used a different class that doesn’t exist.

Fix appears to be changing:

$this->use_woo_nav = class_exists( WooAdminMenu::class ) && WooAdminFeatures::is_enabled( 'navigation' );

to:

$this->use_woo_nav = class_exists( WooAdminFeatures::class ) && WooAdminFeatures::is_enabled( 'navigation' );

In includes/Admin/Settings.php.

Looks like this is just enabling an optional feature, so that *should* be okay.

• This reply was modified 3 years, 7 months ago by rmartell.

Hi all,

@rmartell is correct in that it is an optional feature; however also please note that Facebook 2.3.5 is geared to work with WooCommerce 5.0 and above (it is designed to specifically work with it due to the Admin interface changes of 5.0) as well as WordPress 5.7 – if you are running 2.3.5 make sure to update WooCommerce and WordPress to the latest to ensure compatibility. This means it could cause some errors with lower versions of WooCommerce/WordPress.

If there is a hesitation on updating for fear of additional errors, which is quite understandable, make sure to have a staging site enabled. A staging site is a clone or copy of the Live site, used for testing. You can reach out to your Host if you need to have a staging site set up, as they usually can assist you with this.

If you have further questions let us know!

Hey @nixiack8 —

So we’re doing that (using a staging environment).

We’re currently running WordPress 5.6 and Woocommerce 4.9.1. These versions were latest as of January 19, 2021. Our Facebook rep told us we needed to update our plugin, and we were using 2.2.0; the rep sent us a download for 2.0.3, which I didn’t install because it was older than what we were already using, and instead updated to the latest 2.3.5.

Now we have this issue, and you intimate that there could be other issues since we’re not on WC 5.

What version would you recommend we install on our system? We aren’t ready to perform all the regression testing required to upgrade to WC5.

Hi @rmartell, Please feel free to revert to an older version that was working for you. If that was 2.2.0 please go ahead with that. Given your environment isn’t completely updated, we aren’t able to recommend a specific version that would work for your combination. Ideally, at this point, the idea is to run the latest version possible while not breaking anything, which is going to need a bit of trial and error on your part.

I trust that points you in the right direction, but if you have more questions, let us know. We’re happy to help.