T4ng

Sure, thanks!

Hi,

I received another order in the meantime, which went fine.

Today, there’s no webhook error message anymore:

Still, I reconfigured the webhook.

It’s still not clear what happened, but I hope this problem is behind me now.

Mmh, actually, there might be something wrong. from the WooCommerce > Settings > Payement > Stripe > Settings > Account details [live], I get the following message: “Warning: The most recent live webhook, received at 2024-12-29 13:42:26 UTC, could not be processed. Reason: The webhook was not signed with the expected signing secret. (The last live webhook to process successfully was timestamped 2024-12-24 20:44:24 UTC.)?“

But it doesn’t really make sense since we didn’t touch anything about the Stripe setup for over a month, while we were still able to receive orders with no issue. Until that status issue occured.

In the meatime, I also found this topic. There actually a couple of these, about the same issue.

So for now what I did is click dismiss on WooCommece > Settings > Payment > Woopayment ==> click the 3 dots button > Dismiss (although it wasn’t activated).
This seems to remove the entry from this menu (not the WooPayment main menu entry, but that whole of another story…).

Let’s see what happens.

Hi,

I did it all.

I checked live webhooks from the Stripe platform. They’re all fine.

So I move the live website to Stripe test mode, purged caches and placed 2 orders.

Both moved from “Pending payment” to “Processing” status with no issue.

So by now, no explanation.

I guess I have to wait for another real order to get a better idea of what’s going wrong here.

Hi,

My bad: we use the 9.0.0 version.

We don’t get so many orders on this website, but the two that have come in since the Stripe plugin update are the only ones in this situation.

This website is a bit complex/difficult to duplicate, so I can’t pass it over.

Howver, I have a true local copy on my computer, with the same exact plugin, configuration, and a today-fresh copy of the database. And I don’t face thds issue here.

Therefore, I suspect :

• a temporary issue on Stripe’s side (is this possible – What is triggering the actual status change?)
• a caching issue
• a CDN issue (no CDN on the local copy)

Any thoughts?

Hi, I face the same issue since updating to the 9.0 version. I use this plugin for years, we didn’t change anything to our setup. I didn’t have the logs activated until now, so just activated them.

I can see is from these orders comments: “Order status changed from Pending payment to Processing.” But the order status is actually still “Pending”.

• This reply was modified 2 months, 3 weeks ago by T4ng.

I understand you need revenues, and I understand your solution -WooPayments- offers users benefits, for those who are interested in what it offers.

But many users also made another choice, with other gateways implemetions, plus probably don’t want to add multiple payment methods to their website. Believe it or not, some of them probably have good reasons to make that choice.

So I’m not saying WooPayment is evil, I’m just saying you can’t leave an advertising hoarding on all every admin pages, for all WooCommerce users.

I suggest you basically provide a tickbox, as a WooCommerce Advanced setting, to allow aware users to remove this useless entry menu.

From scratch, WordPress loads everything, everywhere. which allow users to download many plugins and test them straight away, at least in a not-too-much (or properly) customized WordPress instance. But the other side of the coin is that it makes WordPress very prone to high server resources consumption.

Once you’re aware of this, you guys can’t push commercial incentives everywhere in the admin. Elementor is a page builder. Not an AI image generator. We don’t install it for that. You can offer it, but you can’t saturate all Elementor users screens, and suck on their server resources pointlessly, only to push such trivial functionalities (sorry to say, at least for a page builder).

You guys must, at the very least, provide an admin option to fully disable these commercial incentives.

Hi @jonayedhosen,

To my understanding, this issue you’re pointing, basically says that the new expected behavior, long story short, should be:

“Do you know WooPayments? Did you already install it? Have you really really considered installing it?! Because you really really should (considering we really really want your money on every single transaction!). Anyway, as long as you won’t have it installed, I’ll keep showing that useless top-level menu entry. And this behavior will remain until you enabled WooPayment, for every single payment method WooPayment is ready to take a spoon at the cake.”

How about dropping support for non-WooPayment gateways instead?

• This reply was modified 3 months ago by T4ng.
• This reply was modified 3 months ago by T4ng.

Hi,

Glad to see you guys didn’t changed the page address/option again for this last update.
Still, you didn’t remove the menu entry.

• This reply was modified 3 months ago by T4ng.

>> My bad: this is only for Elementor hosted websites. So I believe those for which Elementor provides the hosting solution. Forget it.

Hi there,

Here’s a surprizing update: W3 Total Cache is officially not be compatible with Elementor anymore.

https://elementor.com/help/elementor-hosted-incompatible-plugins/

Hi,

Thanks @gaambo for pointing that gitHub topic.
Thanks @shahzeenfarooq, @ckadenge for pushing it.

I just tested this code, and indeed, it works as expected.

I just hope I won’t need it anymore in 9.4.3 and further versions.
Still needing it would mean Auttomatic pushes its business too hard from the free version.
Renaming it again would just be despicable.

You’re right, concern is the word here. WordPress certainly need money to keep going. But such methods are definitely not the best way to keep it popular over the long run.

I really don’t run for them, but Auttomatic can’t blame competitors for their methods unless the house is in order.

OK, thanks.

Though I feel it’s more a practice concern rather than a technical issue.

Best Regards.

There’s not been any update, nor even an answer to any support topics for months… I doubt this plugin is still under development :/