Draft
Conversation
|
This needs a refresh after WordPress 5.5 It still works, but on WP 5.5 it would trigger a deprecated warning. There should be something like this: |
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.
#2880
What Has Changed
I created a new method in the Caldera_Forms class that gets the list of bad words from WordPress. It has a filter so end users can customize. I then copied logic from here https://gist.github.com/them-es/7c8a120ac868f5c4fc474e53a1266c83 to the loop where fields are validated.
How to test
I'm not sure yet. But I think adding words to the block list and submitting form with those words in the fields.