Richard Bakos

Thank you for the reply, @shameemreza

I will look into modifying the import function myself and check out codeable.io and wooexperts. I just need to be pointed in the right direction.

I’m sorry to say, I have little faith in the feature request page you linked to though. I checked it out and the highest rated feature request, with 184 upvotes, is from August of 2016. The latest feature request listed is from October of 2023. I submitted my feature request and I don’t see it listed. That leads me to believe that they go through an approval process before they are submitted which I don’t remember being communicated in any way after I submitted my feature request. That or the form broke some time in October of 2023. This makes me wonder how many feature requests have been submitted since October of 2023, or at all, that have been waiting for approval or just didn’t make it through.

Do you know anything about this?

• This reply was modified 5 months, 1 week ago by Richard Bakos.

Okay. I have fixed this issue. I feel it may have been an issue of the Cloudflare DNS. I cleared the cache on that and it works now. So I had to clear three caches, CloudFront, CloudFlare, and WordPress/Server. I removed the files from the “rejected files” setting in the plugin and did this cache clearing and it’s running fine, the problem files are being server by the CloudFront CDN without any CORS issues now. I hope this might help others in the future.

Oh, I see, I wasn’t signed in, so the fields weren’t loading. When I sign into the site, the fields are fillable and indeed the input fields themselves are in an iframe as you stated.

This has helped me discover something odd though… noone should have to sign in to place an order because I have guest checkout enabled under “Accounts & Privacy”. I have no idea why these fields can’t be filled out by a guest now. This must be recent because the last order placed via credit card was just a few days ago and it was a guest, they have no account.

That must be a different form, when I search for iFrame in my source, there is no iFrame tag AT ALL anywhere on the page. Feel free to look yourself: https://longhairrecords.com … I have styled the form using CSS, sooo… ::shrugs::

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

When I inspect on this site I work on, the form is not in an iFrame: https://ibb.co/Rcf8mj7

You can see there are styles being applied to the CC# field from a style-sheet, wc-square.scss that is loaded from the local server, not remotely from an external server.

You can also see in the screenshot that the form is using my sites own custom font. That wouldn’t be possible if the form was being loaded from an iframe.

So I am confused why you are saying the woocommerce square plugin’s form is loaded from an iframe. Are you talking about a different form?

You can but you’ll need to create custom css rules in a child theme to override or add to the css rules that wordpress and the square plugin use to render the form/fields. There’s no way to do it from the admin interface.

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.

@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?

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.

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.

If you the option to restore a backup of the site (including the database) prior to installing that new plugin you mentioned, I would do that.

Thank you, Andrew. I will pass this onto my client.

Thank you for the info @stuartduff

Maybe not open source anymore? That link leads to a 404. Looks like the repo was taken down or made private. I couldn’t find it in all of the 154 repos under woocommerce.

This may also prove to be a good resource for those looking to disable this plugin, or any plugin where it isn’t being used on the currently loaded/executed page: https://kinsta.com/blog/disable-wordpress-plugins-loading/