-
Notifications
You must be signed in to change notification settings - Fork 69
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
Fix manual capture status source #9708
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.34 MB ℹ️ View Unchanged
|
d4578ab
to
957a1b9
Compare
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.
This works well. It looks like the reason for that entry in the system status report was to indicate the status of the feature flag, not the setting, but I understand why it became confusing over time. Nice work!
Fixes #9551
Changes proposed in this Pull Request
The manual capture feature flag was removed some time ago, and the code no longer relies on this flag. This PR updates the WooPayments settings class to retrieve the manual capture status from the same option used by other classes.
Testing instructions
Confirm that
Issue an authorization on checkout, and capture later
checkbox is checked,WooCommerce
->Status
showsAuth and Capture
asEnabled
Disabled
with unchecked checkboxnpm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge