site checkout disabled after update

Ran into this myself this morning after updating.

I had to add Opcache support to PHP, enable the opcache.save_comments in 10-opcache.ini, and restart Apache to get it working again.

Let your webhost know this and perhaps that will give enough clues to get your plugin to startup again.

Same issue here – no warning. Only one site had it in autoupdate, but a MAJOR issue. Despite verifying that theopcache function was enabled, restarting apache & NGINX, reinstall the plugin…still broken.

How were you able to roll back to the previous version? Same thing happened to me. Put a ticket into my hosting company and hopefully they’ll be able to enable this but in the meantime, I’m kinda dead in the water!

@earmsby you can get it here https://downloads.www.ads-software.com/plugin/woocommerce-square.3.3.0.zip

Just upload it to your site via plugins add new page.

Are opcache AND the opcache.save_comments both confirmed enabled in phpinfo() on the hosting account in question? We had to chase that one a bit until they both showed as enabled then it worked.

@maxitup – thanks! I figured out how to roll back to earlier version a few minutes after I asked the question. ??

I’m still a little confused, I think. I don’t have the opcache module installed, but it’s still giving me the same error.

Does this mean opcache is now required for this plugin to work, period?

@r4bb1t it does seem that these modules (both opcache AND opcache.save_comments) need to be installed/enabled for it to work again.

While some of the problem is with WC suddenly making a radical change in the plugin, it seems Square is at fault for making a major change in how the plugin interacts with their API…and _may_ have a glitch or two that created this issue.

Square for WooCommerce v3.0 and newer uses the official Square SDK for API communication with the Square platform. Some API responses are cached to improve performance.

When I change to 3.4, both Square settings and payments disappear!

Hi there @maxitup ??

Hi after updating today to latest update i was getting error…

The square checkout option totally disappeared. Rolling back to 3.3 fixed the issue for now.

Thanks for reaching out, let’s figure out why things are not lining up!

I am testing the WooCommerce Square payment gateway option in a test installation of mine, using the latest 3.4.0 version, and everything works as expected. Screenshot showcasing this directly linked here.

Could you make sure the recommended caching settings are set up as required, per the plugin’s documentation, please?

cc @jamiepenner @captainswallow @earmsby @r4bb1t @sevenseconds777

Looking forward to hearing from you!

• This reply was modified 1 year, 11 months ago by anastas10s. Reason: corrected plugin version number

@anastas10s The updated logic is_opcache_save_message_enabled() in WooCommerce_Square_Loader (line 406) in 3.4.0 doesn’t work the same way as it did before (though it’s more robust, for sure), and I think that’s what’s causing the issue (at least for me).

In my case, I don’t have either cache module loaded (Zend Optimizer+ or Zend OPcache), so both $zend_optimizer_plus and $zend_opcache in that function will be false, and so is_opcache_save_message_enabled() will also return false. Unfortunately, is_environment_compatible() (line 349) assumes that means it’s an invalid config, and errors out.

It’s not an invalid config–I don’t even have caching turned on to need to turn on save_comments. I feel like that logic needs another update to account for setups where opcode caching isn’t turned on and the bug it’s trying to fix doesn’t apply.

Response from Automattic (and link to download the previous version if required!):

Thanks for reaching out to us and for checking your server to resolve the issue with OPcache and Square. Could you please roll back to using Square 3.3.0 https://d.pr/f/rqJl4q and see if this still occurs? At the moment, we’re looking into a few reports of this issue coming in. It may be more of a false positive, as in Square still works, but this message is still shown.

While that’s not confirmed just yet, let me know if going back to version 3.3.0 helps remove that error message. It’d likely be worth testing a product sync or test payment as well if that helps quell any worry during this busy time of the year.

For my part, if it helps, it’s not a false positive–the Square plugin doesn’t load any of its features.

Thank you for sharing that in the thread, @captainswallow.

I understand that fixes the issue at your store(s). Correct?

Thank you for elaborating further, @r4bb1t. Could you try reverting to version 3.3.0, as suggested here, and see if the issue persists, please?

We are standing by for your response(s). Cheers!

@anastas10s unfortunately (?) I had already made the required server changes prior to receiving this link, so the plugin is working again for me – but clearly a huge issue that is not currently “user repairable”, outside of downgrading the plugin.