Restrict Content: Add reCAPTCHA for Tags #752
Merged
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.
Summary
Resolves this reported issue of spam subscribers occurring when a creator enables the Member Content functionality, restricting a WordPress Page or Post by Tag, by introducing the option to specify Google reCAPTCHA v3 Site and Secret Keys in the Plugin's settings:
If reCAPTCHA keys are defined, the Plugin checks whether the subscriber exceeds the minimum score, showing a failure if not i.e. they are likely a bot:
Testing
testRestrictContentByTagWithRecaptchaEnabled
testRestrictContentByTagWithRecaptchaEnabledWithHighMinimumScore
Checklist