Hi there,
Thank you for reaching out!
I understand that from time to time, payments through Square fail with an “Error: Square was unable to complete the transaction. Please try again later or use another means of payment” message and reconnecting your site to Square helps.
Which version of Square are you using? In pre-2.0.5 versions of Square for WooCommerce, there was a bug which would cause sites to automatically disconnect from Square every once in a while. Whenever this happens, all payments start failing.
Symptoms: if you’d enable debug logging in WooCommerce >> Settings >> Payments >> Square, whenever this happens, you’d see this error in Square error logs in WooCommerce >> Status >> Logs:
> Unable to refresh connection: Could not renew the token! invalid value for parameter access_token
Updating to the latest version should fix this, although let us know if this is still happening with the latest version of Square for WooCommerce plugin.
We are still running plugin 1.0.38. I’ve been hesitant to upgrade due to the number of issues people have reported on 2.xxx
I have not seen that token error in our debug logs either. I believe it said “unknown error”
-
This reply was modified 6 years, 6 months ago by
flynnstone.
Hi there,
We are still running plugin 1.0.38. I’ve been hesitant to upgrade due to the number of issues people have reported on 2.xxx
I have not seen that token error in our debug logs either. I believe it said “unknown error”
Thank you for confirming! Indeed, version 2.0.0 of Square for WooCommerce was a complete re-write with quite a few functionality changes which came with a few bugs.
Further releases (from 2.0.1 to 2.0.7) mostly contain bug fixes so version 2.0.7 is a lot more stable than the initial 2.0.0.
At this point since version 1.0.38 no longer works – I’d suggest testing the latest version of Square on a staging site and then updating it on the live site.
If you don’t have a staging site – one can be created with a plugin like WP Staging:
https://ww.wp.xz.cn/plugins/wp-staging/
Please also note that the product structure changes after updating to 2.x so downgrading back to 1.0.38 after upgrading is not recommended.
I hope this helps!
Thank you! If i encounter issues after upgrading to 2.0.7, will i be able to downgrade back to 1.0.38? I know you mentioned it’s not advised to go backwards due to product structure changes, but I’m concerned with moving without having a way back. If i disconnect the product sync feature in 2.0.7 will that help with downgrading in the event of issues?
Hi there,
Thank you! If i encounter issues after upgrading to 2.0.7, will i be able to downgrade back to 1.0.38?
If you upgrade Square plugin on the live site – I’d suggest against downgrading to 1.0.38 afterwards.
If you test the upgrade on your staging site with product sync disabled – that should not affect your live site, so you could decide not to upgrade on the live site afterwards.
I hope this helps!
Hi there,
We haven’t heard from you in a while so I’ll be marking this thread as resolved.
Feel free to open a new thread and link to this one if you have further questions though.
Have a wonderful day ahead!
