Repository navigation
Fix classic WooCommerce checkout protection load order (2.10.6) - #116
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Classic WooCommerce checkout silently skipped WebDecoy validation and attempt tracking when WordPress loaded WebDecoy before WooCommerce. The constructor checked
class_exists('WooCommerce')before WooCommerce's entry point ran. Register these callbacks onplugins_loadedafter includes load, while retaining the checkout-protection option gate. Release version: 2.10.6.Validation: 205 dependency-free tests pass; PHP lint and shell syntax pass. The WooCommerce compatibility smoke script now asserts all three classic callbacks exist. In an isolated WordPress 7.1 / WooCommerce 11.2.1 / PHP 8.3 store, classic checkout initially accepted all four synthetic decline attempts; after the fix, attempts 1–3 reached the local decline gateway and attempt 4 was refused with “Suspicious checkout activity detected.” An independent Blocks run likewise refused attempt 4 with
webdecoy_carding/ 403. Separate offline normal test orders completed on both paths. No payment processor or real card was used.