Optimiser plugin update breaks woocommerce plugin

Hello @proleadersacademy,

I was unable to recreate the issue myself and at this point I can not confirm if the PHP warnings are caused by the new SiteGround Optimizer version.?

I would advise you to submit a ticket in your SiteGround account for further investigation. The Technical Support team will be able to identify if the issue is related to SiteGround Optimizer, and if so, they will notify the developers of the plugin.

Best Regards,
Kuzman Stoyanov

I submitted a ticket this morning on this. The 7.3.2 created errors just like that on different sites on our SG cloud server. On each website, each showed a different plugin error. Oddly on the 1st site it was the woo composite plugin, then another showed another plugin on the next.

You can roll back and clear the mem cache and disable the auto-update to fix. Luckily on most, it was just the admin backend which created a hard error, but the error also showed on the front end on the last one I found but only showed the notice at the top and the site was still viewable which was not a WooCommerce site. The last 2 sites, the SG Press was the only plugin that updated, as the 1st instance 2 plugins updated so I alerted them after I was sure it was this plugin.

Hello @proleadersacademy and @futurelink,

Thank you for the report. It appears that some plugins and themes are using the same background library we do. In the version 7.3.2 we have updated the library to the latest version available, and as reported, some of the plugins/themes are not yet compatible with it.

So today we have released a new version of the plugin and downgraded the background process library to the previous version in order to address such issues.

You can upgrade the plugin to the 7.3.3 version and verify the results on your end.

Best Regards,
Elena