montazar

Please get in touch with Klarna Merchant Support regarding the missing countdown modal since the modal is within the <iframe> from Klarna. They should be able to assist you with this.

@dlf123 Regarding the issue with accidental orders, in an upcoming release, we’re going to put a lock to prevent the customer from clicking on the “Buy now” button while they’re about to be redirected.

Hello @alexplay,

We’ll fix this in an upcoming release. You can safely ignore the notice.

If you’re showing debug messages on the frontend, you can disable them.

The popup should appear when the customer is about to be redirected to the confirmation page, showing a countdown. You can see this in our demo store. Please try to place a purchase there by using Klarna’s test data.

Hello @mthelp,

The popup does inform the customer that they will be redirected after the countdown reaches zero, not within five seconds. The actual redirection, after the countdown finishes, is delayed most likely because of server resources. If you check our demo store, the redirection is much quicker than that.

Hello @mthelp,

Which version of OSM are you running? It works on both desktop and mobile in the most recent version (1.5.x) when we test it on our testing environment. If you’re running an older version, please update and try again.

If you’re still experiencing issues, purge the cache in the SG Optimizer, and then deactivate the optimizer plugin on WordPress and settings on your SiteGround account. Check if it works in an incognito/private window.

Hello @malteio,

Can you please try switching to the Storefront theme and see if that helps? I need you to do this to verify that the issue is not theme related.

We managed to identify multiple sources for conflict that caused this issue:

(1) German Market: It was caused by the German Market option Confirm & Place Order Page (General → Ordering). If this feature is activated, clicking Buy now to complete the purchase on the checkout page, the customer will be redirected to a confirmation page where they’re asked to accept terms and conditions and make sure their billing and shipping information is correct before they can proceed to completing the order. Clicking on the button Place binding order to complete the order will redirect the merchant to the checkout page again. This is repeated forever, trapping the customer in a pay-confirm loop.

(2) Elementor: When using Elementor or any other Page Builder plugin, you need to check if you are using the [woocommerce_checkout] shortcode in a regular text widget in Elementor. If you do, you need to use the Elementor shortcode widget or their checkout site page. Elementor do not allow you to run shortcodes in the regular text widget for security reasons.

(3) SG Optimizer: Dynamic content such as the checkout page should not be cached.

I see you’ve emailed our support as well, we’ll discuss there, and I’ll post the resolution here for transparency.

Yes, here is how you can find it. However, if that’s all the errors that you saw, it might not have generated any error log.

I apologize for the belated reply. I had to discuss this with our developers. You can safely ignore these console errors since they eventually succeed. The reason why you cannot see these error message every time is because it is (most likely) cached by the browser. That’s why I couldn’t recreate the issue.

You can read more about it here and here.

Regarding the duplicate orders, please contact our support team so that they can assist you.

Hello Michael,

Currently, there is still some work that has to be done to fully support PHP 8.

Can you please expand on what the error is that you saw? Please check if this also generated any error logs.

Regarding the “internal server error”, in all cases, it has been due to the theme used. Flatsome has already released a new version (v3.14.1) that fixes this for their users. You can verify this for yourself by switching to the Storefront theme, and try to place a test purchase. If you can successfully place an order without any error, the issue is caused by your theme.

Hello Andrea,

Have you followed the setup instructions/requirements? If possible, please provide a link to your store.

It seems like we need to like a closer look into this. Please contact our support team so that they can assist you.

Hello @ansarbhatti,

This is most likely caused by the theme you’re using. Can you please check if any fatal errors log have been generated, and also try to switch theme to Storefront and see if that solves it for you?