• Resolved dingledoink

    (@dingledoink)


    Any help would be great, no manual changes made, but perhaps an auto-update may have broken something?

    2021-05-11T18:18:21+00:00 DEBUG 
    ====Stripe Version: 5.1.0====
    ====Start Log====
    Stripe Payment Request live mode requires SSL.
    ====End Log====
    
    2021-05-11T18:18:21+00:00 DEBUG 
    ====Stripe Version: 5.1.0====
    ====Start Log====
    Stripe Payment Request live mode requires SSL.
    ====End Log====
    
    2021-05-11T18:18:40+00:00 DEBUG 
    ====Stripe Version: 5.1.0====
    ====Start Log====
    Stripe Payment Request live mode requires SSL.
    ====End Log====
    
    • This topic was modified 3 years, 6 months ago by dingledoink.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter dingledoink

    (@dingledoink)

    There is no “BUY” button. We have had 41 abandoned carts in about 8 hours, so this is dire…people can enter their payment info, but not actually process purchase.

    We were receiving orders yesterday. << shrug >>

    Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    Hey there!

    First thing:

    The log you sent in and the issue at hand are unrelated.

    I took a look at your checkout, and from what I can see, there’s some issues with JavaScript on your checkout page.

    JavaScript is being used to hide a terms and conditions page/box, and that contains/reveals the place order button.

    There seems to be a JavaScript conflict/error on the page that is preventing JS from working properly, which will prevent your checkout from working.

    This kind of problem is usually caused by a conflict with your theme or with another plugin.
    ?
    The best way to determine this is to:

    • Temporarily switch your theme to Storefront
    • Disable all plugins except for WooCommerce
    • Repeat the action that is causing the problem

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.

    Thread Starter dingledoink

    (@dingledoink)

    Thanks for your response, that helped me trace it to a Privacy Policy that’s generated by a 3rd party effing things up. Cheers!

    Plugin Support Saravanan S, a11n

    (@simplysaru)

    Thanks for keeping us informed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal Error’ is closed to new replies.