The Generation

Hi again John and thank you for your patience.

Although very rarely, we were able to reproduce the error. We found that if Svea’s API was loaded before our event handler was attached, the observing of the postcode did not work as expected.

We’ve just published a release (1.17.2) which fixes this issue. Please update to this version and verify that it also works on your end.

Have a great day!

Hi,

It should be possible to do the same as in the article.

But, you run this field instead:
do_action( ‘woocommerce_sco_after_notes_field’ );

Then, you storage the field as postmeta on this action:
do_action( ‘woocommerce_sco_before_update_order_information’, $wc_order, $form_data );

Best regards

Hi again.

We think this might be an issue with something in your environment specifically. We have not been able to reproduce this issue anywhere else.

We have sent this issue to our contact at Svea for further help. We will let you know when we have an update.

Hello again!
We have not yet been able to recreate this issue on our end. Would you like to e-mail your login details to our support at [email protected] so that we can troubleshoot this issue on your site?

Hello!
We will look into this and get back to you with an update!

Hi!
Is your environment using https? I tested this issue and could only reproduce it in Safari by using http. This plugin should only be used with https.

Hello again!

If the “Is multiple allowed” is set to NO, we have noticed that even if the customer changes currency it is still the default currency that is being sent to the checkout.
But it sounds like there’s something missing in your settings. Could you please email your support contact at Svea? If they can’t help you they will on their hand reach out to us so that we can have a look at the admin dashboard etc?

Best regards

Dear Jepzor,

Sorry to hear that you are experiencing problems. Is there a tab in the settings for the currency switcher called Advanced? In that case, try switching the “Is multiple allowed” to “Yes”.

Best regards

Hi tobbecokta,

I understand – and it should definitely be possible.

Could you please send the same question to [email protected]? And I will make sure to connect you with a suitable person from Svea.

Best regards

Dear tobbecokta

I am sorry for the inconvenience. Have you reached out to your Svea contact?
They should be able to assist you in installing the checkout.

If there is something pointing to an error in the code they on their hand will contact us and we are happy to help!

Best regards

Dear Isabella!

The plugin should work with that version of WooCommerce but we only update the “supported version” information when we release an update of the plugin.
Therefore it may say we don’t have compatibility even if we do.

Having said that it is always best to clone your site and try on a test environment first as we do not guarantee support above stated versions.

Best regards

Hi Xonium!
We are very sorry for the inconvenience this has caused you.
However it is not standard for WordPress to auto update plugins.
This is triggered manually. Since it is important to crosscheck compability before updating it is not something we recommend to automate.

Again, we are very sorry this happened to you.

Best regards

Hi again Isabella!
Has this been resolved for you?
If not, please send a email to your svea support and they can contact us if they can’t find the problem in your settings.

Best regrads,

Hi,

I see! The best thing here is if we include Svea, so they can troubleshoot this problem.
If you send the same errand to [email protected], I will connect Svea as well, and then we’ll take it from there.

Best regards

Hi!

Hm, did you solve it? I visited the checkout in Chrome just now and it looks fine.

Best regards