This topic contains 3 replies, has 2 voices, and was last updated by 
Admin 8 months, 1 week ago.
-
Posts
-
Hi! I just got everything set up for a Subscriptions product. It’s ALMOST working. User clicks the button, Stripe box pops up, enter the test info, it processes and gives the green check mark (and I can see the test transaction when I look in my Stripe dashboard), but after that I just get a spinning blue circle and it’s not redirecting the user after the purchase.
At first I had no page specified for the product so I thought maybe that was the problem. Then I created a page and specified it, but it’s still doing the same thing.
What have I missed? I feel like I’m SO CLOSE!
Hi, Does the normal product checkout work (just to identify if the checkout issue on your site is happening with the subscription or not)?
Please enable the debug logging option then do a test so you can see if the log file has any error that it is reporting:
Using the Debug Log to Solve Transaction Related Issues on a Site
Are you doing live or test mode transactions? Is the subscription plan created for the correct mode (that you are testing with)? If you created a subscription plan in test mode, you can’t use that for live mode. Need to create new subscription plan for live mode (since the plans are not interchangeable).
I created a regular test product just now (no subscription) and that works. It redirects to my thank you page URL as expected.
For the subscription, I am doing test mode transactions and yes, the subscription plan was created in test mode. I do understand I will have to create a new subscription plan for live mode once we get things working.
I enabled the debug log and tested the subscription again and now, lo and behold, it works! Not sure why it wasn’t working earlier (the blue circle would just spin forever). This time, it still spun for a little longer that I would expect, but eventually the redirect did happen as expected.
Maybe there was a little caching issue (after the update of the plugin, it was likely still using the older JavaScript file from the cache). For now, we will treat this as resolved.
You must be logged in to reply to this topic.