Filter hook for user submitted values #30
Conversation
This file contains 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
I was trying to disable all the fields from account page which I did by overriding `wpum_get_account_fields` but even then there was a possibility that a user can submit form value by creating HTML fields in browser. So added this filter for removing/modifying field data before we can start processing it.
|
Thanks for the PR @kushsharma.
Just so I understand what this is achieving, what's your use case for disabling the fields? |
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.
I was trying to disable all the fields from account page which I did by overriding
wpum_get_account_fieldsbut even then there was a possibility that a user can submit form value by creating HTML fields in browser. So added this filter for removing/modifying field data before we can start processing it.