flowsheff

@lernerconsult

@ajamm wouldn’t even be scratching the surface of what is wrong with the latest release, even if he did offer more information about his particular setup.

Countless websites have lost major revenue as a result of this release. Woo also fails to respond to support tickets in a timely manner in spite of the bloated, bug-laden release. As a paid woo customer myself, I think it’s fair to say that people are simply fed up with the lack of quality control. There’s absolutely nothing wrong with providing legit feedback to woo, when woo is in the wrong here.

(@ckadenge) The main point that woo continues to deflect, and the question on everyone’s mind is: why was 8.5.1 even released to begin with?

Look at all of the responses in the last 72 hours. It’s an absolute disaster filled with endless bugs and bloat. What happened to quality control?

Does woo have plans to get rid of all of the code bloat anytime soon?

@

@sandipmondal you’re making too much sense and asking too much ??

I also despise gutenberg ( I use the classic editor) and it just keeps getting worse and worse with this latest update. I noticed on the checkout page there are new “block” elements being forced whereas before they didn’t even exist.

Do you have any specific info on where you’re seeing the bloat and/or specific elements that were added? Are you seeing most of the bloat on the products page or also elsewhere?

@hastibe I was able to produce the stripe issue and first report the error here: https://www.ads-software.com/support/topic/major-fatal-error-and-conflict-w-8-5-1-and-stripe-gateway/

It was on a completely, empty site with nothing but woo and stripe activated and the error was triggered anytime you attempted to edit users in the dashboard. You’d likely experience the same issue if you attempted to edit a user in the dashboard, though the fatal error may have also been triggered by other unknown actions as well.

Yes, 7.9.1 seemingly fixes this fatal error issue. but they didn’t even bother making an announcement about it. As we sit here now, countless people likely don’t even realize a fix has ben released or that it;’s even related to woo’s own stripe plugin because obviously not everyone updates plugins as soon their released. Woo needs to take some accountability here and actually communicate with their users. Despite having a ticket open, I still have not heard back, and yet this one error alone, clearly affects a huge number of users.

• This reply was modified 10 months, 1 week ago by flowsheff.

@cliqueradar,

As far as I know, there shouldn’t have been any database updates between 8.4 and 8.5, but it would be wise to double check that.

But yes, I am astounded at woo’s lack of support and communication. Nearly 900K active installs for the stripe gateway alone. It’s like they don’t want to publicly admit that the code they released, and their code alone, is the source of the issue. Not too shocking I guess.

• This reply was modified 10 months, 1 week ago by flowsheff.

Half of the fatal errors people are seeing have nothing to do with these security settings. They have to do with Woo’s own Stripe plugin. Updating that will fix half of these issues. Although I’m not doubting the other half of the issues people are experiencing. 8.5+ is a mess.

What is frustrating is that often when there is a support response (See @carolm29’s response above) is that support doesn’t even address the issue at hand. My first and opening post on this specific thread had NOTHING to do with 403 errors – it had to do with critical fatal errors being produced by Woo’s own Stripe plugin. It seems that Woo quietly updated this literally only 2 hours ago, and told no one about it and didn’t even bother making a blog post about it, even though half of the critical errors that were being produced were indeed being caused by that issue.

So incredibly frustrating. Personally, I wouldn’t update to 8.5+ until they get all of the other bugs worked out. According to many others, they threw in a bunch of bloated stuff in this latest version. Eager to advance woo without paying attention to quality control. Quality control seems to be the issue with most things today in society.

It sounds like the simpler answer would be: NO, PayPal Payments doesn’t process existing subscriptions. If you wish for older WooCommerce payments to continue processing using PayPal Standard, then you’ll need to leave PayPal Standard activated but remove it from the checkout process after you begin using PayPal Payments

Did I get that right?

Hi Roxy

My ticket is: 7281791.

There has finally been a response, and I have responded with additional info as this urgent issue still exists.

We do indeed have a valid license. However, we’ve already opened a ticket nearly days ago from within our woo account when this first happened (now 36 hours ago) and still not a single response….So, do we open a new one?

• This reply was modified 1 year ago by flowsheff.

This is still a BIG issue, as we have updated to the latest wordpress, stripe and woocommerce plugins. ALL of our recurring subscription payments are simply failing (both Stripe and Paypal standard) and in the logs they are as following: scheduled action 874898 (subscription payment) failed to finish processing after 3600 seconds.

This is is literally a crisis and should be treated as the highest priority..

Please advise asap!

• This reply was modified 1 year ago by flowsheff.
• This reply was modified 1 year ago by flowsheff.