ttoaster

Hi,

There is no conflict on my site (I have carried out conflict tests; disabling all other plugins, and using your storefront theme), the same issues remain!

If I disable your Stripe and Square plugins and use a third party Stripe Woocommerce plugin (from another developer) which is an Official Stripe Partner, not some fly-by-night solution, the issue does not exist; it works flawlessly and is even easier to setup and customise than yours (and it has more features too!)

The issues are with your code, and as I mentioned before, this is the second time you have broken the card payment gateways (Stripe and Square).

I have absolutely no faith in the developers you are using for these plugins.

The Square on has been particularly unstable, often throwing errors, failing to process payments correctly, screwing up stock settings, etc. To be honest they are a joke!

If your Card Payment Gateway developers worked for me, I would have sacked them long ago…

• This reply was modified 4 years, 4 months ago by ttoaster.

As I’ve had NO reply or suggestions for over 48 hours since my last update, I have disabled all Woocommerce credit card plugins (Stripe and Square) and installed a third party Stripe plugin for Woocommerce, which works just fine.

I will no longer be using any Woocommerce payment gateway plugins as this is the second time in under 3 months that you have broken them (causing lost sales, customers and my hair).

I have absolutely no faith in your payment gateway plugin developers.

@cbdos I am doing the same, but no joy so far.

Last time they broke the Stripe gateway plugin and it caused exactly the same set of issues (no ability to enter card data, etc.) for ALL payment gateways enabled in Woocommerce.

If you find a solution please let me know, and I will do likewise. This is costing me lost sales and customers; what a farce!

Same issue here, and the Stripe gateway plugin is also broken with the latest Woocommerce upgrade. I have all the latest versions installed and my server was working just fine until 16:00 yesterday shortly after I upgraded Woocommerce to the latest version (bad move, on my part)…

I reported the same error yesterday in the Woocommerce support group, I have removed the latest version and re-installed it, and the same file is missing. I suspect it is missing from the install package!

I also downgraded to the previous version, which removed the error message, and let the upgrade install over it again, and the error level returned! The .js file is there, but NOT the .js.map file…

This may or may not be related to the current Woocomerce checkout issue that also started yesterday after upgrading to the latest version of Woocommerce and it broke all the Card Input fields, stopping me from making any sales!

• This reply was modified 4 years, 4 months ago by ttoaster.

Further update, this information form Chrome Console (developer tools) for the Checkout page that is showing the issue with Payment Gateways:

DevTools failed to load SourceMap: Could not load content for https://shop.talkytoaster.me.uk/wp-content/plugins/woocommerce-square/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/assets/js/frontend/sv-wc-payment-gateway-payment-form.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

checkout:978 Uncaught TypeError: Cannot read property ‘setDefaults’ of undefined
at HTMLDocument.<anonymous> (checkout:978)
at i (jquery.js?ver=1.12.4-wp:1)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:1)
at Function.ready (jquery.js?ver=1.12.4-wp:1)
at HTMLDocument.J (jquery.js?ver=1.12.4-wp:1)

If I disable Square, the first error disappears The second one remains), but the issue remains!

Hi,

I have all the latest versions, see below:

WooCommerce Version 4.3.1 | By Automattic | View details | Docs | API docs | Premium support

WooCommerce Square Version 2.1.6 | By WooCommerce | View details
Select WooCommerce Stripe Gateway

WooCommerce Stripe Gateway Version 4.5.0 | By WooCommerce | View details | Docs | Support

I remember the last time it broke, as it caused exactly the same issue, this is not acceptable for a ecommerce platform. I should have moved away from Woocommerce last time this happened as it cost me significantly in lost customers and revenue.

As I stated yesterday, all was working fine until 16:00 GMT+1 yesterday, and the only thing that was updated yesterday, Woocommerce to the latest version at around 10:00 GMT+1

Again, this is costing me significant loss of revenue and customers, not acceptable!

Link to my shop site https://shop.talkytoaster.me.uk

I have multiple customers from around the world using Firefox, Chrome or Safari all reporting the same issue…

I am also experiecing the same issue after updating Jetpack to the latest version, and like you it is causing issue with my site.

My Wordfence log re full of this for every visit made to my site!

For all our sake please fix this obvious typo in your code ASAP!

• This reply was modified 4 years, 5 months ago by ttoaster.

Mihaela,

Thank you for your reply, but I think that my comments are fair and in regard to the issue I reported to you, I have not received any further updates for weeks, nor is the issue logged in your github as needing a fix…

I will not be the only potential customer who is using the Pro plugin which your plugin stops working (after version 2.40.1), why can’t you simply identify what you changed in the plugin betweeb 2.40.1 and 2.40.2 (and every version since)?

As a developer myself, that would seem to be the simplest and most obvious solution? I suggested this to you when I first found the issue.

As to the security issue, it was a MAJOR security flaw, and as I have worked in cycber security (as a deep techie) for over three decades (including penetration testing) if such a major flaw exists is highlights a serious lack of secure coding knowledge… Yes, you have now fixed that issue, but if you haven’t addresed the lack of secure coding (via code review) then I suspect we will see more such security failings.

Hi Mike,

No, I did not downgrade to 3.9, and no it isn’t a Multisite installation, I am still seeing far too much CPU being used since upgrading from 3.9. I am now using 3.9.2 and still seeing far too high CPU and disk activity (I’m assuming it is SQL queries being run in the background by Woocommerce?).

If you have a fix for this, it would be most welcome. Shame it has taken you over 3 whole weeks to respond!

I do this, but with even larger files, up to 3GB.

To do this without download/timeout issues (that is what is causing the issue) you will need to use mod_Xsendfile on Apache (if you are not using Apache, I can’t help).

You will find that it is no longer maintained, however, there is no replacement for this (that I can find), and it works fine on the latest Apache 2.4 version, PHP 7.3, WordPress and Woocommerce versions.

Hope this helps?

I have a backup of the database from before the updated version was installed, but that is not the problem. The problem is that Woocommerce is getting to be more and more of a liability and the level of QA is getting worse…

Hi Andrew,

Thank you for that, but I’ve just confirmed the root cause of the issue…

The conflict is between PM Pro and the Zoho Email plugin. I have confirmed this by using a different mail plugin, and everything works as it should.

You might want to make a note of this as I’m sure I won’t be the only PM Pro user to use Zoho…

Regards,
Martin

• This reply was modified 4 years, 10 months ago by ttoaster.

Any news on this, I have tried all sorts of things, but the issue persists!

Otherwise, is there a way to set the emails to plain text (and strip out the HTML) via your plugin? I couldn’t see such an option.

• This reply was modified 4 years, 10 months ago by ttoaster.