-
Notifications
You must be signed in to change notification settings - Fork 43
fix: update supported gateway check to improve accuracy #2135
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Thanks @leogermani! I totally forgot about this one so it's probably less urgent than the hotfix suggests (we fixed it on the one affected site by disabling the unsupported gateway), but I'll merge it as one anyway! |
## [4.14.1](v4.14.0...v4.14.1) (2025-07-02) ### Bug Fixes * update supported gateway check to improve accuracy ([#2135](#2135)) ([bca370e](bca370e))
🎉 This PR is included in version 4.14.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
All Submissions:
Changes proposed in this Pull Request:
Our supported payment gateway check is sometimes being run too early; it defaults to
false
(no unsupported gateways) so depending when it was run when there are unsupported gateways, it would return a mix of incorrectfalse
values and correcttrue
values.This update tries to run the check a little earlier and save the value, to improve the check's accuracy. It also changes the default to
true
so if the payment gateway check can't be run in time for whatever reason, it will default to unsupported gateways being set.How to test the changes in this Pull Request:
Note: please test each checking step (where you test the modal) in a couple incognito windows, just to try to spook out whether it's just intermittently working 😅
Of the original testing steps, please also check:
Other information: