Hello @koseb
Thank you for reaching out to us, we are here to help.
We have seen some instances of this issue before, but it seems to not occur with many merchants. There are 2 things we would advise you to try in order to correct this behavior:
- Try changing the field “Default customer location” to “shop country/region” in the page WooCommerce > Settings > General, and see if that improves the situation.
- You may want to perform a full conflict test to rule out eventual issues with the theme or a different plugin. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for WooCommerce and PayPal Payments to see if the behavior persists. Here’s a guide that explains the steps in more detail: How to test for conflicts.
If this does not get you any improvement in the situation, please let us know, so we can try again. If you want to share more details of your site (logs, screenshots, etc.) you can also engage us directly via these instructions.
Pending your response.
Kind regards,
Joost
Hello,
since we did not receive any response or follow-up questions from you, we will assume you got this working to your requirements. If you still have any more questions for us, please open a new thread, because we will mark this one as resolved.
Kind regards,
Joost
Thread Starter
koseb
(@koseb)
Hi Joost,
sorry for the late feedback. After several tests, the problem unfortunately persists. What else can be the reason for this? We should fix this as soon as possible.
Hello @koseb
We could take a look ourselves, but will have to get your system report, logs and possible the screenshots of the settings of your site (some aspects of it).
It might be easier to share this via a private engagement with us (instead of on this public forum). You can find the instruction for this here: https://paypal.inpsyde.com/docs/request-support/
(please add the URL of this thread in the ticket as well)
It would also help to hear more details from you about how often this occurs and if you are able to reproduce the issue? Have you already tested this (and reproduced this) on a staging site?
Pending your response.
Kind regards,
Joost
Thread Starter
koseb
(@koseb)
Hi,
ok thank you. I sent you a ticket.
I have the same problem.
I get the error MISSING_SHIPPING_ADDRESS when I choose certain countries such as: St. Martin (part of France).
MISSING_SHIPPING_ADDRESS The shipping address is required when shipping_preference=SET_PROVIDED_ADDRESS.
With the plugin:
WooCommerce PayPal Payments
Version 2.1.0
Thread Starter
koseb
(@koseb)
Hello Daniel,
here’s how I solved the problem. Deleted the content on the checkout page and added the default WooCommerce shortcode [woocommerce_checkout]. IMPORTANT: Make a backup of the page before and test it on a staging or test page first.
I use the Divi theme and there are several shortcodes stored on the checkout page that can be used to customize the page. Unfortunately there seems to be a problem Divi shortcodes. With the standard WooCommerce shortcode the page is not as customizable as the Divi page but at least everything works with it.
I just looked at it and you are right, with native checkout it works perfectly… this is a problem for me. Thanks for your reply.
hi @joostvandevijver, hi @koseb
I have the same issue – get the message on the checkout page all the time MISSING_SHIPPING_ADDRESS The shipping address is required when shipping_preference=SET_PROVIDED_ADDRESS.
Although some users somehow managed to pay successfully with
PayPal 😮
Is there meanwhile a known solution for the bug?
My plugin:
WooCommerce PayPal Payments Version 2.2.2
Theme Kallyas
just an addition – customers who managed to use paypal live in Denmark
Thread Starter
koseb
(@koseb)
Hi @piofre, unfortunately not. Currently we still have it so that we use the standard checkout page from woocommerce. As described above, so first make a backup of your page in case something doesn’t work, then delete all the content on the checkout page and then just insert the shortcode [woocommerce_checkout]. Save and you’re done. After that it worked for us again… If this doesn’t help, I think you better open a new ticket or contact the support of the plugin directly.
