We are aware of this issue and plan to get it fixed in the 1.2.1 follow-up to the 1.2.0 update which will be coming soon.
We’ll update here once the fix has been done so you can grab it early if you want.
It happens to me, even without the coupon. Can’t go forward, beacuse of “Error processing checkout. Please try again.”
Thank you!
We would need to see a copy of the log file generated by the plugin to get an idea of what might be happening there. Please submit a ticket here and provide that.
Thread Starter
Dave
(@vinnitski)
Could you roughly state when the update will be available? Especially when working with influencers this is a crucial functionality for us. Please let me know.
Thank you.
It’s probably going to be a few weeks. We’re still wrapping up the 1.2.0 update right now.
Thread Starter
Dave
(@vinnitski)
Hi, just saw that there is already an update available!
Awesome work! Thank you so much!
Ah, sorry for the false hope, but we had to re-arrange some of our issues / version plans because of hot fixes that needed to go out.
You can see the different milestones here: https://github.com/angelleye/paypal-woocommerce/milestones
Within each of those are the issues planned for that milestone / version. When important things come up, though, sometimes we have to make adjustments to that, so if you want to stay updated it’s good to review that from time to time.
We’re working to get through all milestones as quickly as possible!
Hi there,
I am having the issue of “Error processing Checkout, Please try again.” I have confirmed that the server is using TLS 1.2 and it is on by default. I have installed another plugin called Braintree for Woocommerce Free and it has a test for TLS 1.2 and it comes up fine and in sandbox mode and testing a credit card payment, it all works perfectly. I would prefer to use your plugin. Would you know why I am seeing this error when I am usign your plugin.
Thank you very much.
@paulluxford, I’m sorry for the delay responding. Do you have logging enabled in the plugin? Please make sure logging is enabled, then reproduce the problem, and then submit a ticket here with the log file attached.
