Mark

Hi Norm, thanks for jumping in actually, you’ve seem to highlight the issue here and you are using a SUBSCRIPTION.

For us, what’s strange is that these are not subscriptions.

And of course our host tracked back our records and did not find any server backups, migrations, etc. And no we are not caching /checkouts/

The issue happened twice around PaymentIntent API in stripe and could be a random glitch from Stripe on their end though I don’t think they’ve been much help here.

As of right now I am disabling a few plugins and seeing what happens.

There is a key flawed logic from WooCommerce’s developers or whoever made the decision here:

1. Customer legit paid
2. So never ever mark the order as FAILED, even if there is an error in some secondary data point like Payment Intent.

Like, let’s get real here, as a business owner, we just want to make sure $ is in the bank and non-reversible, flag it but don’t FAIL it.

oh sorry, here is a screenshot of the freeze:
https://www.dropbox.com/s/4en192qqs7klg26/Screen%20Shot%202020-04-26%20at%205.23.20%20PM.png?dl=0

obviously look at others having this problem but it does not seem like they had the exact same issue.

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

apologies for including a link!

there are 1801 issues on Git.

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

OP so smug, I love it.

Thanks for that 0.01s of page load boost and the ability to made TWO columns of text easily. Ohhh and blocks.

Sorry but this is really not going to convince readers to buy products.

Two columns of text don’t make the story any more compelling to read.

Different CSS for each “block” of text doesn’t mean it’s the New York Times.

What does run a business is the ability to produce content quickly and efficiently (using VA’s if needed)

Good for you for making a “developer” friendly editor for WordPress I guess