The text link ‘–OR–‘ persists when Apple Pay button is not present

Hi @mikecooter

I had been using Stripe with my WooCommerce store for the last few years with no problems – but I was unable to activate the new ‘Express Checkouts’ features (I kept getting pop-up notice saying ‘Error Saving Settings’).

While researching the error I saw the new WooCommerce Payments plugin and deciede to switch over – and it is mostly working fine.

Thanks for using our products!

However, if I tick the checkbox next to ‘Product Page’ (on the Express Checkouts settings page) the Buy Now fails to be displayed on any of the Product Pages, yet the ‘–OR–‘ separator is still shown. This results in a confusing arrangement of the Quantity buttons, then ‘–OR–‘ then the Add To Basket button.

That’s really odd! I don’t have any issue when enabling Express checkout, Apple Pay on product pages, this kind of issue that you’re facing is usually caused by some conflicts.

First thing is to try switch to a WooCommerce compatible theme like Storefront or Twenty Twenty and see if the issue is still there or not.

Here’s a more extensive explanation in our docs about conflict testing: https://docs.woocommerce.com/document/how-to-test-for-conflicts/

I hope that helps!

Let me know how it goes!

Thanks for the feedback Sol, I’ll look into and let you know. ??

Hi Sol,

I followed your doc (NB: Meks Quick Plugin Disabler is no good in this situation since it disables WooCommerce & the Payments plugin!) – but none of my plugins were causing the issue.

Finally got down to the bare bones – and switched the active theme to ‘Twenty Twenty One’- and the Buy Now button did indeed display correctly.

Huge shame since I’m using Avada, and they are usually very well integrated with all WooCommerce features.

Perhaps something has been overlooked, maybe the <iframe> containing the call for “https://js.stripe.com/v3/elements-inner-payment-request-xxxxx&#8221; on Product pages isn’t allowed by Avada?

I did notice that on Cart & Checkout pages the ‘Buy Now’ button was placed using <script> rather than <iframe> – that seems to be the only major difference?

Any insights welcome, for the time being I’ll just have to remove the button from my product pages.

Thanks.

Hi @mikecooter

What a great intel!

Thanks for taking the time to do the conflict test and it comes down to Avada that isn’t compatible with WooCommerce Payments Express checkout button on product pages.

Perhaps something has been overlooked, maybe the <iframe> containing the call for “https://js.stripe.com/v3/elements-inner-payment-request-xxxxx” on Product pages isn’t allowed by Avada?

I can’t really confirm. But if that is the case, then I’d suggest reaching to Avada to alert them about it. I think they should be in a position to make their theme compatible with our WooCommerce Payments plugin which is getting used widely now.

If you have any other questions, do not hesitate to let us know!