• Resolved Bernard Lemieux

    (@blecreateur)


    I got fatal errors upon going to the checkout page after activating the new payment form (after Re-authenticate as well). The problem went away after going back to the legacy form. Using Divi, everything is up to date.

    Is there anything I missed? Do I have to recreate the webhooks, or completely reinstall the plugin in order to make it work with the new form?

    BTW, I have recently created a new website using this plugin with no issues with fresh install using the new form by default.

    I have the logs. Not sure how I should share them.

    Please advise, thanks.

    Bernard

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

Viewing 9 replies - 1 through 9 (of 9 total)
  • Zee

    (@doublezed2)

    Hello Bernard Lemieux,

    Thank you for contacting WooCommerce support.

    I understand that you’re getting fatal errors on the checkout page after enabling the new payment form, but the issue disappears when switching back to the legacy form.

    To understand the issue better, please share your error logs.
    You can paste them into https://pastebin.com and share the link here.
    Also, share your site’s System Status Report the same way.

    Once I have more information, I will be in a better position to assist you further.

    Best regards.

    Thread Starter Bernard Lemieux

    (@blecreateur)

    Hi,

    I replied to your email directly since I was not sure if I should share the links publicly.

    Is this OK ?

    THnaks,

    Bernard

    Zee

    (@doublezed2)

    Hello Bernard Lemieux,

    Thank you for your reply.

    May I ask which email you replied to?

    Please note that we do not have any other means to communicate except this forum.
    If that helps, you may use https://www.quickforget.com to post information here.
    It will still be public but will automatically be removed after some time.

    Looking forward to your response. 🙂

    Thread Starter Bernard Lemieux

    (@blecreateur)

    Oops, I replied to the “no reply” emails I receive when you place your replies here. Sorry.

    Here is the link: https://quickforget.com/s/1a1821c8ded4ea84008062843ec19242ef63413cca73d9e8

    Thanks,

    Bernard

    Hi @blecreateur,

    Thank you for your response and for providing the requested details.

    The error message indicates that your WordPress site is missing or has an invalid function called “hide_my_icons,” which is triggering a TypeError in WooCommerce and its Stripe payment gateway integration.

    After reviewing your System Status Report, I noticed that you have multiple customizations through plugins and the Divi theme. Just to clarify, “hide_my_icons” is not a built-in WordPress or WooCommerce function—it was likely introduced by a plugin, custom code, or your theme.

    To help identify the root cause, could you try disabling all Divi-related plugins and temporarily switching to the Storefront theme to see if the issue disappears?

    Additionally, I checked your checkout page and didn’t encounter any fatal errors. Could you clarify where exactly you’re seeing the error? Is it on the front end of the checkout page or in your error logs?

    Let me know the results after switching the theme and disabling the Divi-related plugins. Looking forward to your response!

    Thread Starter Bernard Lemieux

    (@blecreateur)

    Hi,

    Sorry for the delay. You were right. I had the following custom function to remove Stripe Woocommerce Credit Card Icons:

    add_filter( ‘wc_stripe_payment_icons’, ‘hide_my_icons’ );

    I commented it out and the issue went away.

    Is this normal? I will have to do the same to all my sites… If the filter is available to be used why is it causing an issue after upgrading to the new payment form? Should I avoid reactivating the filter?

    Thanks,

    Bernard

    Zee

    (@doublezed2)

    Hello Bernard Lemieux,

    Thank you for your reply.

    I understand you resolved the issue by removing your custom code for hiding Stripe payment icons.
    Good job finding out the solution!

    It’s possible that custom code conflicts with the other site code. Please note that Custom code falls outside our support policy. I recommend consulting a professional WooCommerce developer to update the code. You can find good developers at Codeable or WooExperts.

    You may also post your question in the Woo Community Slack for insights from other users.

    Let me know if you have any questions.

    Best regards.

    Thread Starter Bernard Lemieux

    (@blecreateur)

    Thanks for your help. We can close this ticket.

    Bernard

    Hi @blecreateur,

    Thank you for letting us know that the issue is resolved. I’m glad we could help clarify the conflict with your custom code. If you have a few minutes, we’d love it if you could leave us a review: https://wordpress.org/support/plugin/woocommerce-gateway-stripe/reviews/#new-post

    Thanks again for your feedback!

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Fatal errors upon going to the Checkout page after activating the new paiement f’ is closed to new replies.