crezzysue

Reporting back to say that the subscription feed was cancelled once we updated to the latest Stripe API.

Reporting back to say that we were using an old Stripe API in the Stripe account’s dashboard.

We’ve updated to the latest API version.

Does the plugin cancel the subscription when it tries to charge more than the number specified by the installment feed? So having a draft invoice for the 3rd payment might be normal?

We did a test charge set to charge daily for 2 payments, but it kept running and wasn’t cancelling. It could have been the outdated API in our Stripe account.

I’ll report back with an update.

I’m replying back to report that the plugin is working now.

Gravity Forms Stripe Add-on instructions say to setup a Webhook in “Live” mode – but if you’re in Test mode in Stripe, you also need to have a Webhook setup in “Test” mode or your subscription transactions won’t make it to your site’s database. https://screencast.com/t/v1i6iK16

Make sure the site has SSL (https) and that Basic Auth directory protection is removed if testing on a dev/staging site.

I’m experiencing the same issue.

Wordpress 4.8
Gravity Forms 2.2.3.6
Gravity Forms Stripe Add-On 2.3

The subscription is not canceled per plugin settings. The subscription is still active. We’re in test mode luckily.

I found this from Gravity Forms that might be useful:
https://www.gravityhelp.com/documentation/article/cancel-a-stripe-subscription-after-n-payments/

• This reply was modified 7 years, 7 months ago by crezzysue.

Hi @ontraportfrank,

This was actually a local build of a client’s site. I setup a dev site on the same server as the production site and updated all plugins and then the WP core and all is fine and working as expected. Must be something with my local setup. I will investigate. Thank you for your notes about the wp-config file and the non-fatal PHP warnings. Thank you again for your time!

@edwardslabs and @wittyoctopus, thanks for letting me know that simply making a folder in the correct directory worked for both of you.

So maybe it was the renaming without spaces that did the trick! I think I was having caching issues with WP Super Cache settings. Seems to be ok now.

Thanks again you guys!

Just wanted to chime in on this subject: I’m using MAMP to work on a WordPress site on my local machine as well, and was having issues with the CSS not showing up for my child theme.

I followed the “renaming/removing the space” advice from wittyoctopus, but I also had an ah-ha moment when I realized I was not installing my child theme properly. I had simply been putting the child theme folder in the “themes” directory and refreshing my browser instead of uploading a zipped folder and actually installing it.

It wasn’t until I removed the folder and refreshed the page to delete it, and a WordPress message appeared on a gray background that said “cheatin’ huh?” – I then realized I was doing it wrong ?? Oops!

Just wanted to put that out there in case someone else is doing it wrong too and having the same issues. I did it the proper way – uploading a zipped folder to install it – and all is well now. Phew! Good luck!