• Resolved cromagrickman

    (@cromagrickman)


    Using Formidable forms with the Stripe payment addon, and discovered that a form submission was causing an API error with Stripe. Contacted the developers of Formidable forms, and they suggested turning off plugins one at a time. WP Super cache seems to be the one causing the error.

    Typically, one submission goes through fine, then if try to do a second submission, it errors out and puts an API call error in the browser console. Clear out the cache, and then you do one more submission, but then it errors out on the second try again. This behavior is repeatable.

    I’m guesssing there’s some option in the advanced settings of WP Super Cache that is causing the issue. Here is the API error in the console:

    Failed to load resource: the server responded with a status of 400 () api.stripe.com/v1/payment_intents/pi_1HKWgGHjIinhTH6WHopesgw3/confirm:1

    Deactivating WP Super Cache and I can do multiple submission in a row with no errors.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Unfortunately I’ve never used Formidable Forms but I presume there’s some part of it that has to be not cached so that Stripe can reply, maybe. You can exclude that URL in a setting in the advanced settings page. Look for “Add here strings (not a filename) that forces a page not to be cached”.

    Or Formidable Forms can make sure their plugin makes that page uncacheable by defining the constant DONOTCACHEPAGE.

    You could also enable the debug log in the plugin and then see what URL is causing the problem when WP Super Cache serves it from the cache.

    Thread Starter cromagrickman

    (@cromagrickman)

    That is extremely helpful! When I have time to test, I will look into logging. Thank you!

    Thread Starter cromagrickman

    (@cromagrickman)

    Marking as resolved.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WP Super Cache causes API errors with Stripe on Formidable forms’ is closed to new replies.