robertrosanke
Forum Replies Created
-
Hallo @itrechtkanzlei ,
danke für die Aufklärung. Werde den Anwalt kontaktieren und auf das Ticket verweisen. DDer rest wird dann vermutlich seinen Gang gehen.
Thema erledigt. Danke!
Hallo @itrechtkanzlei ,
danke für die ausführliche Erläuterung. Habe die Einträge nun via Plugin UI gelöscht. Die wp_options Tabelle hat entsprechend reagiert und wir haben nun knapp 100 KB weniger im autoload.
Super. Thema erledigt. Vielen Dank!
Forum: Plugins
In reply to: [WooCommerce] Woocommerce Quantity Syncing IssueHello,
I just wanted to link to another ticket that might be relevant.
We also have an external system connected to WooCommerce.
- When it updates the stock quantity via REST API, the WooCommerce REST API returns outdated stock quantity in the response, which is causing a lot of error logging in the external system.
- In our case, it’s the other way around: the data is updated correctly in the WooCommerce shop, but the JSON response that WooCommerce sends is incorrect. It’s essentially returning the outdated product object, or at least not all properties are up to date.
- This causes the external system to believe, when checking the response, that something has gone wrong. (Which it hasn’t, everything is okay.)
We’ve noticed that the error only occurs when we have the “WPML String Translation” plugin active, and therefore we’ve opened a ticket with WPML.
Reading this ticket, I’m wondering if there was a change between WooCommerce versions 10.2.2 and 10.3.4 that might be related to the API. We’ve been experiencing this error since then.
The page is in German and may need to be translated using Google Translate if anyone wants to read it:
I wanted to leave this information here because it seems relevant. I understand that separate tickets should be created for different topics. If this isn’t helpful, please just ignore it. However, since two people are already having problems with the REST API, it might still be of interest to WooCommerce support.
@karthik92 I wish you the best of luck with troubleshooting. Such errors are often not easy to analyze and the fix can be time-consuming.
Forum: Plugins
In reply to: [Klarna for WooCommerce] klarna loads on every pageThanks for the quick reply @awaatklarna .
November 17 sounds good, that’s not long to wait.
I won’t bother with it now just for a week and hope that your plugin update comes quickly.Kind regards,
Robert
Forum: Plugins
In reply to: [Klarna for WooCommerce] klarna loads on every pageHello @klarnaplugin @saraatklarna ,
To be honest, I haven’t checked the code yet to see if you’ve already solved the problem with a plugin update.
According to other angry commenters, probably not.
If you’re not going to provide an update for this improvement, which could be implemented in a few minutes, I would at least appreciate an answer to my question.
Is my suggestion from the second answer safe to implement, or would it cause any problems with Klarna?
If this can be implemented securely, all of us who are annoyed by this issue will at least have confirmation and know that we can solve it ourselves if you (for whatever reason) are not going to do so.
Kind regards,
Robert
Hello @saivutukuru ,
Thank you for the detailed information.
I left it over the weekend and saw that everything is still fine today.
So we haven’t reconnected anything.
(We did that just a week or two ago, so I don’t know why I would need to do it again.)Everything seems to be working fine so far, and the email from Stripe was a false alarm.
Thanks, and have a great week!
Are you sure that this checkbox needs to be displayed when only one payment method is active and this function would not even make sense at the moment?
(In the other thread I linked to above, a support representative said that it’s perfectly okay for this not to be visible because we only have one method active. I’m surprised by the contradictory statements.)
We have fixed maintenance windows and no more time. It’s Friday evening here, 5:30 PM local time.
Version 10 of the Stripe plugin was only released two days ago. It’s highly unlikely that a checkbox that has supposedly been around for several versions would suddenly appear.
The changelog also does not mention this checkbox. What do we do now?
What happens if we don’t activate this box because it is not displayed?
Hello @lovingbro ,
Thank you for your prompt reply.
Here is a screenshot of what it looks like in our backend:
- https://snipboard.io/cyEmwC.jpg (Language: German)
- Under the advanced settings, we only have a debug option.
- System Status Report: https://pastebin.com/ivZJQ4Jp (available for one day)
I have never seen the setting you describe in the backend.
I would tend to rule out a plugin conflict, as we almost exclusively use the well-known standard plugins. Payment processing only PayPal, Klarna, and Stripe plugins for WooCommerce.
Hello @saivutukuru ,
You’re right. If WCML has an incompatibility, many people could be affected. Here is the link to GitHub.
The issue has just been closed. The next WooCommerce update should therefore resolve the error.
Hello @mosesmedh .
Just to help us narrow this down further — could you please confirm whether the issue still occurs when WPML/WCML is disabled? Also, have you had a chance to reach out to WPML/WCML’s support team about this conflict?
Thank you for offering to help us with the WPML issue.
We have already created an issue in the GitHub repository for WooCommerce, and a solution is already on its way with a pull request.
By default, the WooCommerce Stripe extension performs both authorization and capture simultaneously. This means that when a customer completes the checkout process, Stripe immediately captures the payment — it doesn’t depend on order status hooks running afterward.
Thank you for this information. That was exactly what we needed. Many thanks. So everything is fine.
Have a nice weekend!
Hello @awaatklarna ,
Thanks for your help. Everything seems to be working fine with the temporary workaround. The ticket can be closed.
Hello @awaatklarna ,
Thank you for your feedback.
We had an internal meeting last week and tried everything out. It seems that we cannot issue refunds if an order has not yet been captured.
- All affected orders appear to remain open in Klarna for 30 days.
- The payout is delayed, but it appears to take place even if it has not been captured.
However, it seems that a workaround would be to log into the Klarna dashboard and manually capture all orders affected by the WCML error once a week.
The Klarna dashboard synchronizes the capture process in the WooCommerce backend, so we can continue working there as normal. (Refunds are working.)This is a minimal additional effort that we can cope with temporarily until WPML/WCML fixes the error.
Do you see a problem with this approach, or is it okay for now?
Thank you for the clarification. Could you please raise a support ticket here in order for our team to look into this further. The team requests details such as how the auto-capture is implemented, logs and screenshots of the woocommerce order notes, so please also include that in the support ticket.
Thanks for the link to your support page.
I haven’t opened another ticket for now. Maybe—if you don’t have any concerns about the manual capture process—we have a temporary solution and can save ourselves more time on this issue.
Hello @inpsydekrystian ,
Thank you for your reply. We are glad that PayPal works out of the box for us despite these unfavorable circumstances.
Well, in this specific case, their response makes a bit of sense, because the issue indeed goes beyond what any payment gateway plugin can control and sits between WooCommerce and WCML.
I see it differently. I am simply asking about how a plugin works. I have neither requested nor submitted any custom code. I just want to know how the plugin works so that I can act correctly.
Perhaps I communicated my request in a technical way, making it sound more complicated than it was. That could be the case.
The ticket can be closed. Thank you for your support, @inpsydekrystian , that was very helpful.
Hello @mosesmedh .
Perhaps my request was too technical, making it seem as if it was about an individual implementation. That is not the case.
We simply have a case where, due to a plugin conflict (WPML/WCML), the core WooCommerce hooks related to order status changes have failed in certain circumstances for many orders.
I just want to know whether this is a problem for the Stripe plugin (we only use credit cards via Stripe) or not. At first glance, everything looks fine. Stripe still seems to be processing payments correctly.
With Klarna for WooCommerce, for example, we now have to capture orders manually in the Klarna dashboard, because otherwise payments may be delayed, as Klarna relies on the woocommerce_order_status_completed hook, which is no longer guaranteed to fire.
PayPal for WooCommerce, for example, says that everything is fine. They capture the payment directly when it is created.
The Stripe plugin is currently the only plugin that refuses to provide us with information.
I’m simply interested in understanding how the Stripe plugin works. Do I have to manually capture payments via Stripe credit cards if the status hooks may not fire, or not?
