Update 2.0.72 Has Broken Plugin

  • Resolved gidders28

    (@gidders28)


    3 years, 6 months ago

    I have just updated Stripe Payments from 2.0.70 to 2.0.72 and now when I test & click buy now I get this error message “Error occurred: Class “Stripe\PaymentIntent” not found”

    The plugin is in test mode at the moment

    The plugin was working fine before the update.

    Any ideas?

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support mbrsolution

    (@mbrsolution)

    3 years, 6 months ago

    Hi, can you disable and delete the plugin. Then install a fresh new copy of the latest version. Then carry out a test?

    Let me know what happens.

    Kind regards.

    Thread Starter gidders28

    (@gidders28)

    3 years, 6 months ago

    If I disable & delete the plug in, will all my existing products be retained for when I reinstall?

    Plugin Support mbrsolution

    (@mbrsolution)

    3 years, 6 months ago

    Hi, you won’t loose the products you have created in the plugin. However, just to be on the safe side, can you create a database backup.

    Kind regards.

    Thread Starter gidders28

    (@gidders28)

    3 years, 6 months ago

    Hi, I’ve disables, uninstalled & reinstalled the plugin.

    I still get the same error message “Error occurred: Class “Stripe\PaymentIntent” not found”

    I’ve reinstalled v2.0.71 & that works (although it takes a veeerrrryyy lllooonnngg time to redirect to the custom thank you page

    Plugin Support mbrsolution

    (@mbrsolution)

    3 years, 6 months ago

    Thank you for providing more information. I have submitted a message to the developers to investigate further your issue.

    Kind regards.

    Plugin Author mra13 / Team Tips and Tricks HQ

    (@mra13)

    3 years, 6 months ago

    This could be a PHP version issue. What version of PHP is being used on your site? Your hosting provider can answer this question for you.

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

The topic ‘Update 2.0.72 Has Broken Plugin’ is closed to new replies.