-
Notifications
You must be signed in to change notification settings - Fork 51
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
Remove support for legacy form checkout #3691
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.
@claudiulodro this could be a hotfix, if we wanted it to go out sooner
I'm OK sending it through the regular release flow just to benefit from the alpha release testing/process. It's pretty straightforward to add this code snippet to a site in an emergency in the meantime though. |
Hey @claudiulodro, good job getting this PR merged! 🎉 Now, the Please check if this PR needs to be included in the "Upcoming Changes" and "Release Notes" doc. If it doesn't, simply remove the label. If it does, please add an entry to our shared document, with screenshots and testing instructions if applicable, then remove the label. Thank you! ❤️ |
# [5.13.0-alpha.1](v5.12.2...v5.13.0-alpha.1) (2025-01-23) ### Bug Fixes * add supported gateways check ([#3650](#3650)) ([74f7773](74f7773)) * **corrections:** replace deprecated sanitize method ([#3694](#3694)) ([ce50e24](ce50e24)) * remove support for legacy form checkout ([#3691](#3691)) ([46a3c16](46a3c16)) * **wcs:** expire manual subscriptions after on-hold duration ([#3681](#3681)) ([658416c](658416c)) ### Features * add custom bylines ([#3667](#3667)) ([3f45a6f](3f45a6f)) * rate limit checkout attempts ([#3678](#3678)) ([d275524](d275524))
🎉 This PR is included in version 5.13.0-alpha.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
All Submissions:
Changes proposed in this Pull Request:
Removes support for the legacy form-based WooCommerce checkout. Other than for backwards compatibility, I believe the main purpose it's still around is to support browsers that have JS disabled, but that's not something we support (especially since it wouldn't work with reCaptcha).
How to test the changes in this Pull Request:
Simplest way to verify that it's been removed:
die( 'ATTEMPTING FORM CHECKOUT' );
here in your Woo plugin in thecheckout_action
method.wp eval-file scriptfile.php
before applying this patch. Observe that the response contains thatATTEMPTING FORM CHECKOUT
string within it.Other information: