gerold1968
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] 10.8.0 Update ErrorManual download of the plugin file and re-installing it did the trick in my case.
Forum: Plugins
In reply to: [WooCommerce] 10.8.0 Update ErrorSame here… oh, you WOO Ninjas, this is the second time an update of the plugin gives us these errors. And as it seems for a lot of people out there its the same. Shit happens, but what about testing your updates a little better before releasing?
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] Intermittent Webhook IssueHi, I meant to log if a webhook is sent with no errors (200) BUT the order isnt updated to paid.
I am not sure about the root cause by now, I cant reproduce it on staging, so troubleshooting is difficult.
Best Gerold
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] Intermittent Webhook IssueHi, I figured it out for my setup. Suggestion: log if a webhook is recieved but no actio taken?
Best Gerold
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] Intermittent Webhook IssueHi Clayton,
I was able to narrow this down further.
For affected orders (order-pay / retry cases):
payment_intent.succeededwebhook is received (200 OK)- Action Scheduler job
wc_stripe_process_deferred_webhookis created and completed - but the order remains
pending - no transaction ID
- no “payment completed” order note
Example scheduled action data:
- type:
payment_intent.succeeded - order_id:
23555 - payment_intent:
pi_3TExngHodsEAhbgg555cOu
From reviewing the code of the plugin, the issue seems to be in the deferred handler:
- it ignores the scheduled
payment_intentargument - it does not sync
_payment_intentmeta from the webhook payload - it relies solely on
process_payment( $order ) - and it has no logging if that returns
WP_Errororcomplete_payment = false
So in these cases, the webhook is received and processed, but the deferred handler silently exits without completing the order.
This seems to affect order-pay / reused pending orders specifically, where local order state and Stripe state may be out of sync.
Best,
GeroldBest Gerold
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] Intermittent Webhook IssueHey there, thx for super-fast reply with tech insight. I appreciate!
Best Gerold
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] PaymentRequest GatewaySolved! Thx so much for superquick reply and pointing that out. Would have cost me days…
Have a good one!
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] PaymentRequest GatewayThx for quick reply!
All the same plugin versions, php, even same server.
Best g.
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] GooglePay not showing on CheckoutThx for clarification!
Forum: Plugins
In reply to: [Payment Plugins for Stripe WooCommerce] GooglePay not showing on CheckoutHi there, thanks for yoyur quick reply.
I guess I found the reason: Payment is dependent on third-party-cookies and these are not allowed if you are in incognito-modus. This was why Gpay didn´t show up. In normal mode it works as intended.
But Google has announced to block third-party-cookies entirely, so this may become a big problem!?
Best Regards
Hi, thanks for quick response. Tried again in a staging environment and now it works. No idea what happened. Maybe a caching issue …
Best
I’m not aware of such development, I’m afraid. Could you share further details on where this is published?
This is what can be read within your own plugin settings:
Enable the legacy checkout experience
If you enable this, your store may stop processing payments in the near future as Stripe will no longer support this integration. Learn moreFurthermore giropay payment gateway isn´t working with the legacy version right now and customers cannot pay, but are shown an error message:
The Sources API has been deprecated, and we are no longer allowing new integrations. Please follow our migration guide to integrate with the Payment Intents API: https://stripe.com/docs/payments/payment-methods/transitioning
In this case, you can continue using the legacy checkout. All you need to do is turn off the new checkout experience and use the shortcode on the checkout page.
Hmm… seems to be not such a great idea as the plugin itself says the legacy checkout will stop working for some payment methods in a month or so…
You can also seek help from the following:
Are you serious? You suggest to hire a paid expert to get false translations of a plugin correct?
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] giropay not working anymoreHi, found out what happended in the meantime: giropay-payments don´t work with the legacy checkout. Using the new checkout experience it works.
…but sadly opens the gate for new problems… see my other thread on this forum: https://ww.wp.xz.cn/support/topic/translations-not-working-since-update-to-8-1-0/
Hi, no it´s about some strings I cannot translate using the new checkout experience. I guess this is because everything there is loade via i-frame as I found out by inspecting the site.
In my case the strings for eps-payments and giropay-payments have to be changed to fit my needs, whcih was no problem with the legacy checkout…
Pls have a look at the screenshots: the translation for these strings has to be changed:
https://snipboard.io/0jW7b5.jpg
https://snipboard.io/jLvsN8.jpg
- This reply was modified 2 years, 1 month ago by gerold1968.
