luzat

@mrclayton If I use the buttons from within the payment gateway, I can confirm my purchase in PayPal and get returned to the thankyou/order-received page. In that case, I do not need the separate buttons at all. There may be other flows in some Woo configurations, where you are returned to the checkout page and have to click the Place Order button, but this doesn’t apply for us.

There are 3 issues for me if the separate order placement button does not work:

1. All other payment methods still use the order placement button. It’s inconsistent for me as a user if I get a warning instead and have to use another button only when using PayPal. Apart from technical reasons, I would expect it to just redirect to PayPal.
2. There is some content between payment method selection and order placement button. The user might want to check out the content, but will have to scroll up again to get back to the PayPal button to complete his order instead of just being able to use the button which is most often expected to be at the end of the page.
3. We also do have a somewhat shop-specific issue, where the payment provider selection in some cases gets hidden by us and the user only sees the order placement button. It’d currently not be possible to finish the order if PayPal was selected in that case.

As a hack, I was already considering to click the primary PayPal button through JS when the order placement button is clicked, but that’s not possible given the iframe.

Given that the button works as expected if Use Place Order Button is enabled, I would expect that there was some way to invoke the same actions even in case it wasn’t enabled (at least through code). There is some JS code,which seems to generate the click error (order_button_click) if there is no order id, but in place of generating that, generating the order and redirecting to PayPal would be very helpful.