louisekrokedil

Hi @aizazali017 ,

We have also recieved a support ticket from you regarding this issue directly with us at Krokedil. We will continue the troubleshooting in our support and when we have solution we will also update this forum post.

Hi,

The code changes that were discussed in this thread and recently released were based on a workflow that is no longer applicable for this purpose. As a result, our changes did not deliver the expected outcomes for either you or us.

The solution currently implemented in the plugin is the one described here, which works effectively when inventory is managed by WooCommerce. Since adhering to WooCommerce standards is the primary goal of our plugin, we will not be making any changes to this functionality:
<a href=”https://docs.krokedil.com/krokedil-general-support-info/pending-payment-orders-and-held-stock/ “>https://docs.krokedil.com/krokedil-general-support-info/pending-payment-orders-and-held-stock/

That said, we do recognize shops may have different requirements and we strive to support as broad of a range of options to meet those requirements where possible, appropriate, and reasonable. To help improve this issue, we will introduce a new action that triggers whenever the modal is closed, regardless of the reason. This will enable developers to write custom code tailored to each specific store’s needs. Once the new action is implemented and documented, we will share the links here for your reference.

Additionally, you could create a cron job to set unpaid orders to failed after a specified timeframe from the order’s creation.

Appreciate the complexity and importance of this topic, and hope this comment and additional updates will help improve handling of Klarna pending orders in your shop.

Hi @robertrosanke ,

Please get back to us if you are having issues with the latest update of the plugin and the failed order status functionality. And if you would like us to take look at any specific order where the customer reported issues with the checkout process please let me know.

Hi @mattheus ,

The script should only be manually added to the body if you are not using our Klarna for WooCommerce plugin and still want to use On Site Messaging. Our plugin already use the script which most likely is the reason for the error “Another Klarna Web SDK was already included in the page…”. Since you are using our Klarna plugin you need to remove the manually added script from the body, but keep the two shortcodes. Then also add this filter to display On-site Messaging on all pages.

Does these changes help?

Hi @tehcook,

A new version 3.9.0 of Klarna for WooCommerce has been released which includes a fix for the “Textdomain was called incorrectly” notice.

You can see the full changelog/technical information here.

Hi @mattheus,

From version 3.7.0 of Klarna for WooCommerce there is a new plugin settings page. With this new settings page the Client ID was not migrated, as you already noticed you need to go to the plugin settings and add the Client ID for all countries again.?

You also need to whitelist your site URL in your Klarna account settings. Go to your Klarna merchant portal –> Payment Settings –> Client identifier –> Allowed origin, register your URL there.
Please see our documentation here.

Regarding the PHP warning in the console. In your Klarna plugin settings for On-Site Messaging, have you set the Cart Page Theme and Product Page Theme to Dark, Light or Custom?

Hi @mattheus,

When i visit this product https://luizaxl.nl/11-delige-keukenkastenset-bewerkt-hout-artisanaal-eiken/ the price is updated correctly in the Klarna on site messaging widget when changing the variation.

I was able to recreate the issue regarding the price not being updated in the Klarna on site messaging widget i my local testing environment, the issue was solved when i created a new variable product. If you are still having issues, try and create a new variable product and see if it works then.

Hi @mb00 ,

Thanks for letting us know, i have mentioned your options on how to address this in our internal task and we will look at this further when time permits.

Hi @mb00,

Sorry for our late reply. This is not an error, these messages are for debugging purposes. I have created an internal task for us to discuss whether it is possible to hide these messages.

Hi @robertrosanke,

Regarding ”customers have not canceled and even ask us why the order has not yet arrived”. We would like to have a look at these orders and the logs from when the orders were created, if we can see any issues/errors. But that information is sensitive and should not be posted here in this public forum. Please also create a support ticket with us via our Krokedil support form here and mention in the ticket that it is related to this forum thread. Then when we have more information about the orders we will post an update here in the thread too.

Hi,

The order note “customer aborted purchase with klarna” means that the customer started the payment process but before it was finalized the customer chose to abort and not finalize the purchase. This is not an issue, just a note that the customer did not want to complete the purchase.

It is WooCommerce standard behavior to create a Pending Payment order in WooCommerce when the payment process starts. The status pending payment means that the order is not yet paid for, the order will not be created in Klarna until the order is paid for. Having Pending Payment order does not necessarily mean that an issue has occurred.

We are currently working on a new workflow to use the failed order status in WooCommerce and the release is planned for early next year. Thanks for giving us all details on this!

Hi,

Could you please send what spam message it is? Is it related to textdomain?

Hi,

This error should not effect your checkout, only trow messages in your debug log. We have already made a fix for this and it will be included in the next release of the plugin.

Thanks for letting us know!

Hi Jacob,

I am not able to recreate this issue in my test environment. When i test the amount is updated correctly when changing the shipping method after an error has been triggered.

If you try and use the Redirect checkout flow in Nexi Checkout instead, does that solve the issue?

This issue might be caused by a compatibility issue with either the theme that you are using or any other plugin that you have activated on your site, please try the following:

• Try and change the theme to Storefront which is the theme our plugins are tested for and see if that helps.
• If that does not help try and deactivate all plugins except for WooCommerce and our Nexi Checkout plugin and see if the issue is solved. If so, activate all plugins again one by one to see what plugin might be causing the issue.
• Also go to WooCommerce Status –> Tools, Clear customer sessions and Clear template cache.

I suggest that you try this in a staging environment of your site to make sure not to effect your live site and customers or create a backup of your site. You can read more about staging environments here. 

Hi,

I suggest that you contact your Klarna merchant support regarding this to make sure your API keys are correctly configured and/or if Klarna can see more information on this 405 error code.