Support » Plugin: WooCommerce Payments » Early Access Payment methods disappear when user selects another then WCP again

  • Resolved w-sky

    (@w-sky)


    Hello,

    I am observing this problem with all browsers when I have the new payment methods (“early access”) activated on my site:
    I am seeing the WooCommerce Payments methods when the checkout page is loaded and can use those. But when I click a non-WCP payment method e.g. “Invoice” and then “WooCommerce Payments” again, none of the online payment options are shown.

    Hint: To quickly add a product to the cart and see my checkout page, go to “Certificates/CO2 bonds” in the main menu.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 17 total)
  • Plugin Support nathvi V. a11n

    (@nathvi)

    Hello @w-sky

    Thanks for your message!

    I tested the checkout and can reproduce what you describe:

    1) Selecting “Popular payment methods”: https://d.pr/i/bWHB9z
    2) Selecting Invoice or Direct Transfer: https://d.pr/i/x0LHge

    When trying to select WooCommerce Payments again, nothing is shown.

    Looks like something is conflicting with the payment methods on checkout specifically. Are you using a second gateway in your site?

    I’d also like to better understand your site. Could you please send me 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, you can paste it here in your response.

    Once we have that information, we’ll be in a better place to help.

    Thread Starter w-sky

    (@w-sky)

    Hello, thanks for your reply! No, we are not using another gateway.

    But I found the culprit using Site Health Troubleshooting mode: This is a conflict with the plugin “Germanized for WooCommerce” by @vendidero

    Once this is deactivated, the WooCommerce Payments module works without the problem described above. This plugin does some changes to the checkout page.

    Hi there,

    Germanized triggers a checkout refresh via $( 'body' ).trigger( 'update_checkout' ); on switching the chosen payment gateway. That’s nothing special and should be handled by the WooCommerce Payments Plugin too. E.g.:

    $( document ).on( 'change', '.payment_methods input[name="payment_method"]', function() {
       $( 'body' ).trigger( 'update_checkout' );
    } );

    Cheers

    Plugin Support Ahmed M. a11n

    (@nagdy)

    Hi @vendidero,

    Thanks for the information you provided.

    That’s nothing special and should be handled by the WooCommerce Payments Plugin too.

    Can you please elaborate more here? Do you think there’s a bug in WooCommerce Payments?

    As far as I can see, without “Germanized for WooCommerce”, the issue does not happen.

    Getting more info on this will help report this further.

    Looking forward to hearing back from you.

    Thread Starter w-sky

    (@w-sky)

    One more information: The bug does not occur when only the “classic” credit card payment method is active in WooCommerce Payments.

    When I disable “early access” payment methods, there is no problem.

    Plugin Support Chris Moreira – a11n

    (@chrism245)

    Hi @w-sky!

    To be on the same page. What happens when you have enabled “Early access” in WooCommerce Payments without the plugin “Germanized for WooCommerce”?

    There are, are any errors, or it works as expected?

    Thread Starter w-sky

    (@w-sky)

    Yes, it does work as expected. The user can switch the payment method several times on the checkout page and no problem. It is much quicker too, because it does not reload each time and instead just slides back and forth.

    Hi @w-sky,

    Thank you for this additional information – I have a quick question; we have been seeing the Early Access area conflict quite a bit with the Germanized for WooCommerce PRO version – not necessarily just Germanized, but with the PRO extension.

    If you have the PRO extension, disable that (leave Germanized regular running) and do a test. If it works, then you can report it to the developer as they already know this is an issue with that and are plotting a fix for it.

    WebSprite

    (@contentsprite)

    Apologies if this is hijacking the OP but I had the same issue with the entire iframe payment form disappearing. It happened whenever the customer used a dropdown selection (for example, to change their country, choose to ship to a different address, etc). The iframe came back only if the customer refreshed the entire page.

    After chasing this for days and trying every possible troubleshooting measure (changed theme, deleted and reinstalled the plug-in, turned off all other plugins, different browsers and devices, logged in and not logged in users, clearing caches, downgrading versions or woo and wc payments) and nothing working, and reading dozens of similar issues (most often the solution seemed to be custom coding whatever a DOM is to avoid one part of the code loading before another) that involved the disappearing iframe – disabling early access fixed it.

    At the same time, thinking it was unrelated, a new user couldn’t create a customer account in the checkout page. I enabled guest checkout to get around it and focused instead of the disappearing payment form. Well that’s fixed as well. Something in the early access feature loading conflicts with other page events. I wish I knew more tech stuff to explain it better, but just in case anyone else is going through the same headache, they should try disabling early access. Only takes a second to see if that’s the problem.

    I had only recently enabled it and it didn’t occur to me it could be the issue until I saw this post.

    Edited to add: After the payment formed disappeared the customer saw the error “We could not retrieve data from the specified element. Please make sure the Element you are attempting to use is still mounted.”

    • This reply was modified 2 months, 1 week ago by WebSprite. Reason: Include error message
    Thread Starter w-sky

    (@w-sky)

    Hello @nixiack8

    If you have the PRO extension, disable that (leave Germanized regular running) and do a test. If it works, then you can report it to the developer as they already know this is an issue with that and are plotting a fix for it.

    I have tested this, disabled Germanized Pro and left only the standard Germanized plugin active, but I am seeing the same error. Once another payment method is selected, WooCommerce Payments disappear and do not reload when selected again.

    Plugin Support Nagesh Pai – a11n

    (@nagpai)

    Hi @w-sky

    Since the issue noted here does not appear when using another Payment gateway (PayPal standard, as noted earlier), the issue is very likely restricted to Germanized.

    I see that you have rightly opened a post with the developers of Germanized here
    https://wordpress.org/support/topic/germanized-stort-das-neue-woocommerce-payments-plugin/

    You may contact them further and see if they have anything specific they want us to check.

    Thanks

    Thread Starter w-sky

    (@w-sky)

    Hello @nagpai PayPal was not mentioned here before by anyone.

    The problem occurs with WooCommerce Payments, new “early access” payment methods enabled, and WooCommerce Germanized. The payment methods disappear when the user selects any other payment method and then selects “WooCommerce Payments” again, which should be “Popular payment methods” actually but the description changes too.

    The problem does not occur with standard (old) WooCommerce Payments credit card payment method, also it does not occur without WooCommerce Germanized.

    I will remind the Germanized developers.

    @contentsprite as far as I understood, your problem is absolutely not the same when the entire payment form is disappearing when changing form details. I suggest to re-post with a new thread.

    Plugin Support Nagesh Pai – a11n

    (@nagpai)

    @w-sky Thanks, I will discuss this with the developers and see if there is anything that we need to fix on WooCommerce Payments. Since this feature is still in early access, I will check if this is a bug waiting to be fixed at our end.

    Plugin Support Nagesh Pai – a11n

    (@nagpai)

    Hi @w-sky . It looks like the issue is expected to be fixed in our upcoming release. It should be available in the next few days. Thanks for reporting this persistently.

    Thread Starter w-sky

    (@w-sky)

    Thanks @nagpai. Looking forward to the updated release!

Viewing 15 replies - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.