Version 3 breaks Checkout

I understand the frustration but you have to remember this is a free plug-in. You get what you pay for. The amount of time and resources it would take to test their updates with every possible combination of themes, plugins, hosting and server environments is mind-boggling and not at all feasible for a small development team building something free for the community. Which is why it’s nice to have these support forums where they can try to figure out why it doesn’t work in your particular setup.

Also when you have a big update like going from 2.x.x to 3.0 you should expect significant, breaking changes. I never jump right into a big update like that. I wait for ‘all’ the bugs to get exposed and get patched. This is why I subscribe to various plugins support forums. Once it looks like the dust has settled and things are fixed, then I’ll apply the update. This is also why it is, imho, unwise to set everything on auto update.

Hi Richard,
Not sure what to do with that reply? Not helpful at all. If there was a paid alternative I would certainly use it. I understand new updates are prone to failure which is why I was asking what has been changed so the community can fix it themselves. Your suggestion to hold off on updating my plugins and leave my business open to security threats its neither helpful or correct.
But thanks for chiming in?

Well, you obviously haven’t looked very hard cause there are paid alternatives:

https://codecanyon.net/item/woosquare/14663170
https://codecanyon.net/item/woocommerce-square-up-payment-gateway/19692778
https://codecanyon.net/item/woocommerce-square/22136956

In fact, there is even a free alternative:

https://www.ads-software.com/plugins/woosquare/

Just seems like you have an issue with taking your time to actually do any research….

This update has nothing to do with security. If it did, they wouldn’t be telling people to downgrade back to 2.9 while they look at the issues people are having with it’s functionality. What I suggested, if you read between the lines, is researching major updates before applying them, being aware of what you are doing and the risk involved. My site’s that use woocommerce square are working properly. Are yours? You see, I know how problematic this plugin is and know it’s past, because I research them and just don’t install and update everything willy-nilly, especially when it’s coming from a small development team.

And if you really want to know what has changed. Just compare the code of 2.9 against that of 3.0 … The amount of changes in the version is too much to just gloss over in a support forum and the repo is private so I wouldn’t hold my breath for them to publicly post some detailed explanation of what exactly has changed in their code-base. ALso, for a brief explanation of the changes, there is something called a changelog and it’s publicly available.

• This reply was modified 2 years, 6 months ago by Richard Bakos.

Version 3.0.0 has broken the checkout for me too @bloodygeese we are currently rolling back the plugin to previous version and sending a fully document example replicating the issue to square.

@resonancedesigns a bit harsh. As a payment gateway they are making a commission on every sale it’s in their interest to ensure it functions.

Clearly we are not all as smart as you.

We will be testing future updates on staging before pushing.

@paolovino No, the maker of this plugin receives absolutely no commissions on any sale you or any store makes using their plugin. Where did you get that from?

Hello @bloodygeese and @paolovino !

Thank you for reporting this issue.

We are very sorry for this inconvenience that was caused by the latest release of the Square plugin.

Our developer team has just now released 3.0.1 version to patch this issue. (Refer to our changelog for confirmation: https://www.ads-software.com/plugins/woocommerce-square/#developers)

If you have a staging site instance, please test the version to see if the issue can be resolved on the site.

If you still experience any issues with Square plugin, please open a support ticket at https://woocommerce.com/my-account/create-a-ticket/

Thank you so much for your patience with us on this.

@resonancedesigns Your negativity is not helping anyone and you sound very pompous.

Can a mod please delete his passive-aggressive insulting comments? I do not see a report button?

Some excerpts:

“You get what you pay for”

“Well, you obviously haven’t looked very hard cause there are paid alternatives”

“Just seems like you have an issue with taking your time to actually do any research”

“My site’s that use woocommerce square are working properly. Are yours?”

Wow! These might be ban-worthy?

Lol… Oh pleaaaase…. Nothing was personally attacking or insulting….

I met passive aggresiveness and snideyness with the same:

“Your suggestion to hold off on updating my plugins and leave my business open to security threats its neither helpful or correct.
But thanks for chiming in?”

“You get what you pay for.” … what is false about that? You aren’t paying a premium so you shouldn’t expect the same level of support you get for the paid alternatives. And he said (as if he actually knew) that there were no paid alternatives. I corrected him. Was the paid alternatives I provided, that he said he would “certainly use” if they actually existed, not helpful? I gave him an alternative. Multiple alternatives. Seems like that would be helpful to me, especially given the claim that they would use it. ::shrugs::

What I was giving was actual helpful advise on how to properly administrate a site that is supposed to generate revenue and make wise decisions to mitigate risk of bringing down something that is supposed to be making you and/or your client money.

All too often I see people complain about things breaking because they just update without actually looking into the risks involved with the update then come here and blame the developers and accuse them of passing the buck onto someone else. Which is exactly what OP was doing, and it’s simply not true. It’s incompatibility issues as a result of major changes to the plugin that they felt were necissary and they can’t possibly make it work with every combination of every plugin and hosting, and themes, etc. They just come in here and go “FIX IT! I AM LOSING MONEY” and don’t want to put in any effort into looking into things themselves. They just expect the devs to wave a magic wand and make it work for them.

With someone with a name like “Webmaster1234” I would think that you would understand these things. And again, I know it’s frustrating and I have been frustrated with this plugin and countless others over the years but I worked through those issues without throwing shade at the devs and accusing them of passing the blame.

Hello everyone,

We are definitely interested in any bugs that are encountered using any of our extensions. When you run into a bug, what the developers need are steps to reproduce it. They have no way of fixing a bug that they can’t experience for themselves.

So they need to know the minimum plugins required to see the problem as well as the exact steps needed to see the problem. If you share that with us, we can create an issue on GitHub so the developers can address it.

It’s definitely not possible to test for every server setup or possible combination of plugins with any plugin release. We do test quite a bit before a version is released but it really is impossible to test every possible scenario. If you do run into some problem, letting us know the details helps us, help everyone.

Thanks for working with us on this!

Can confirm the Square plugin version 3.0.1 has problems loading input fields in some browser versions (Firefox and Chrome)

View post on imgur.com

I also received this error notice:

Error Details
=============
An error of type E_ERROR was caused in line 555 of the file
/nas/content/live/website/wp-content/plugins/woocommerce-square/includes/Plugin.php.
Error message: WooCommerce\Square\Plugin::add_currency_admin_notices():
The script tried to execute a method or access a property of an
incomplete object. Please ensure that the class definition
"SquareConnect\Model\Location" of the object you are trying
to operate on was loaded _before_ unserialize() gets called or provide
an autoloader to load the class definition

Hey @webmaster1234,

Please open up a new thread for this topic. Thanks

We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.