Ryan Ray

Hi,

I’m sorry that these messages aren’t dismissible, but I do think they are important for everyone to see. Perhaps our team errs on the side of caution to make sure anyone who views the plugin pages sees that message.

As you’ve noted there is a timeline set out hopefully giving everyone time to make a plan to test the PayPal Payments plugin on a staging environment. In this case PayPal Payments has all of the features of PayPal Checkout and adds more to it.

When you do have time to test the plugin on a test/staging site we’re here to help figure out any issues you might run into. In my testing I’ve not had issues using the plugin on a staging site, but obviously we’re ready to help investigate and fix anything you might find in your testing.

That doesn’t mean we expect you to run into issues, just as our Stripe extension is always being updated fixing issues so will PayPal Payments. 🙂

• This reply was modified 4 years, 7 months ago by Jan Dembowski.
• This reply was modified 4 years, 7 months ago by Jan Dembowski.

Hi @argentum,

Hopefully an update to your sites PHP version is the fix. Even if not getting your site using the latest version of PHP 7 would be a great idea. There’s many performance and security improvements getting on version 7.

Let us know either way, thanks!

Thanks for the update @roadsunknown,

Glad you have something that is certainly working. I’ve not had a moment to try and test this myself, but I’ll aim to ASAP and try to follow up here with what I find.

Perhaps as well another community member will beat me to it as well. 🙂

Thanks again!

Hi @volcomjon & @devsc2768,

You should be able to submit a ticket directly to us and we could get a bit more information to help troubleshoot what might be going on. You can open that ticket that puts you in touch with us by choosing Stripe in the form here: https://woocommerce.com/my-account/create-a-ticket/?form=ticket

Let us know once either of you’ve done that. We can then find the ticket and investigate further to see what could be causing this error. Thanks!

Hi @arquetipos,

it is possible to add MercadoPago as a payment option? This plug in is very used in Latin America.

Thanks for the question regarding MercadoPago. Was this specifically to add MercadoPago support to the new checkout block, or were you just asking in general for MercadoPago support in WooCommerce itself?

I ask as I see a payment method for Mercado here. –> https://wordpress.org/plugins/woocommerce-mercadopago/

If you wanted Mercado to work in our Checkout block that would be up the developers of the above extension to add support for. That bit isn’t finalized yet so I would maybe assume most payment method developers are awaiting the official and finalized resources for how they can make their extensions compatible with the new checkout block.

I hope this helps so far, let us know if you’ve got further questions. Thanks!

Hi @rgroves,

Thanks for contacting about this odd position of the shipping modal. Is there anyway you would be able to try a quick conflict test to rule out other plugins from potentially causing the issue?

Also could you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”.  Once you’ve done that, paste it here in your response.

Read more about plugin and theme conflicts in our [Self-Service Guide](https://docs.woocommerce.com/document/woocommerce-self-service-guide/).

**How to test for conflicts**

The best way to determine if the issue is being caused by a theme and/or plugin is to:

1. Temporarily switch your theme to the [Storefront](https://woocommerce.com/storefront/?aff=10486&cid=1131038) or [Twenty Twenty](https://wordpress.org/themes/twentytwenty/) theme.
2. Try to reproduce the problem with the shipping modal. 
If the problem is resolved, it is a theme conflict. If not, continue to the next step.
3. Temporarily deactivate all plugins except WooCommerce. You can do this manually or use a plugin to help (see below for tools).
4. Try to reproduce the problem again. If the problem is resolved, it is a plugin conflict. To figure out which plugin is causing the problem, continue to the next step.
5. Reactivate your other plugins one by one, testing after each, until you find the one causing conflict.

For more detailed instructions, check out [How to test for plugin and theme conflicts](https://docs.woocommerce.com/document/how-to-test-for-conflicts/).

Please let us know how that goes.

**Tools to help with troubleshooting**

[Meks Quick Plugin Disabler](https://wordpress.org/plugins/meks-quick-plugin-disabler/)  will remember what plugins you had active when you switch it back on.

You can clone your site to a staging environment and perform tests without modifying your live site or impacting customers. Many hosts provide staging facilities, so it’s worth checking in with them. It’s also possible to do it using the free [WP Staging](https://wordpress.org/plugins/wp-staging/) plugin.`

Hi @buddhika23,

If there’s not adequate methods via the REST API, I did come across this post from SkyVerge that seems to outline a way to get all refunds no matter of the order status itself. –> https://www.skyverge.com/blog/get-woocommerce-refunded-orders/

Maybe that would help if nothing else does for the REST API.