Breaking conflict with Gravity Forms Stripe Addon v3.4

  • This plugin creates a breaking conflict with Gravity Forms Stripe Addon v3.4. It works fine with v3.3. https://www.gravityforms.com/add-ons/stripe/

    When LittleBot ACH for Stripe + Plaid is installed with Gravity Forms and Gravity Forms Stripe Addon (no other plugins, default 2020 theme) the payment form does not submit and returns a 500 error.

    I can supply access to the plugin and/or a staging environment.

    Their changelog for 3.4 states “Fixed an issue with Stripe feeds conflicting with feeds from other payment add-ons in the browser.”
    https://docs.gravityforms.com/stripe-change-log/

    Their developers say: “The other plugin is likely including an older version of the Stripe SDK that doesn’t include the necessary Stripe\PaymentIntent class mentioned in the error and that outdated SDK version would be preventing our version of the SDK bundled with the Stripe add-on from being included that does include the class mentioned in the error. Version 3.4 of the add-on uses different methods and classes to handle payment processing than 3.3, so that is likely why you’re not seeing it when running 3.3 as the methods and classes used in that version are probably included in the version of the Stripe SDK they are including.”

    and “The real crux of the issue is the other plugin should not be including any version of the Stripe SDK unless it is actively being used, this is what our add-on is programmed to do with its version of the SDK. I will however pass your feedback on to the Product team for future consideration of adding a fallback for older versions of the SDK.”

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author justinwhall

    (@jwind)

    Judging by their response, they say some sort of error log. Could you kindly pass that along?

    Thread Starter Razorfrog Web Design

    (@razorfrog)

    Yes of course: 

    [10-Apr-2020 21:48:23 UTC] PHP Fatal error:  Uncaught Error: Class 'Stripe\PaymentIntent' not found in /var/www/staging.razorfrog.com/htdocs/wp-content/plugins/gravityformsstripe/class-gf-stripe.php:5755
Stack trace:
#0 /var/www/staging.razorfrog.com/htdocs/wp-includes/class-wp-hook.php(287): GFStripe->create_payment_intent('')
#1 /var/www/staging.razorfrog.com/htdocs/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters('', Array)
#2 /var/www/staging.razorfrog.com/htdocs/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#3 /var/www/staging.razorfrog.com/htdocs/wp-admin/admin-ajax.php(175): do_action('wp_ajax_gfstrip...')
#4 {main} thrown in /var/www/staging.razorfrog.com/htdocs/wp-content/plugins/gravityformsstripe/class-gf-stripe.php on line 5755
    Plugin Author justinwhall

    (@jwind)

    Hmmm, that’s an error from another plugin. I premium one no less. Sort of hard to debug. I’ve released an update that may help?

    Regardless, this plugin will soon be deprecated in favor of an addon to LittleBot Invoices. https://littlebot.io/plugins/littlebot-invoices/

    Thread Starter Razorfrog Web Design

    (@razorfrog)

    Thank you for the update, that fixed the issue!

    Bummer to hear that the plugin is being deprecated – it fills a really useful one-off payment use case for us and we already have an invoicing system. Let me know if we can help support the continued development somehow.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Breaking conflict with Gravity Forms Stripe Addon v3.4’ is closed to new replies.