-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a payment source redirects to wrong URL #289
Comments
Having the same issue here when trying to add a payment source. Any luck in resolving this? |
Unfortunately, the issue remains. I had to make an ugly workaround with redirects and session variables. None of the related issues are getting any attention from the team, so I wouldn't get my hopes up for a fix anytime soon. |
That is unfortunate, thank you for the update. |
@peterurban would you mind sharing your workaround please? Suffering from the same issue. Thanks |
It's not pretty, but it works for my use case. Essentially, I added a redirect in my 404.twig, pointing the user to the desired url. In my case, I also need to keep track of the chosen plan, for which I use a session variable ("plan"). If this bug gets fixed at some point, the system would just send users to the correct redirectUrl and skip this step.
|
@peterurban thanks for the pointer. Skipping the
|
Thank you @antcooper - that worked for me. |
Hey @peterurban @antcooper I can’t seem to replicate this in local development in various browsers, I can't see how production would be any different unless they were configured differently. What URL does it generate for you in local vs production? I get this: |
@lukeholder this works fine locally in DDEV. On Servd in Staging and Production, the URL is as below. I've shortened all the hashed values for readability. The
|
When adding a payment source as part of a subscription flow. The page redirects to:
/index.php/actions/commerce-stripe/customers/confirm-setup-intent
and notindex.php?p=actions/commerce-stripe/customers/confirm-setup-intent
causing a 404.Redirect works as expected in local development, but not production.
Form:
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: