4.0 | Edge Case Critical Error

Beta
#1

@alexander – Tested an update on a client’s multisite/woo network and all worked decently well. Pushed the update live this morning and got a critical error on one of the sites. More details in note.

#2

Hey @DoncoMarketing,

Can you let me know what version of WordPress is being used? We added support for lazy loading images based on the WordPress configuration but it requires at least WordPress 5.5 wp_lazy_loading_enabled was part of WordPress 5.5

Here’s a shim you can put in to stop the fatal error without updating for now.

if ( ! function_exists( 'wp_lazy_loading_enabled' ) ) {
  function wp_lazy_loading_enabled() {
    return false;
  }
}
#3

For the point release I’ve wrapped our call in function_exists to avoid this error on older WordPress versions.

1 Like
#4

Hi Alexander. Much appreciated. As mentioned, this may very well be an edge case but we’re noticing a pretty significant Woo issue that we can’t seem to identify. Kinsta has been digging into it too for roughly 5 hours and hasn’t gotten to the bottom of it. The only thing that reverts the issue is downgrading to Pro 3.2.3.

Sorry to do this for all who are reading but further detail in note.

#5

Hi @DoncoMarketing,

I’ve confirmed Pro 4 works on multisite with the latest WordPress and WooCommerce versions. In your case I wouldn’t recommend upgrading pro until at least WordPress and WooCommerce are updated.

Do you have a staging site? If you can get everything updated and are still having issues I could login and take a closer look.