-
Notifications
You must be signed in to change notification settings - Fork 799
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
Contact Form: Defensive coding against bad hash #20923
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
|
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.
This looks sane. 🚢
Moving to in progress. When rebasing on WP.com, the WP.com linters aren't happy with it so I'll fix it in this PR so we avoid having any sync issues. |
Caution: This PR has changes that must be merged to WordPress.com |
Caution: This PR has changes that must be merged to WordPress.com |
Caution: This PR has changes that must be merged to WordPress.com |
Caution: This PR has changes that must be merged to WordPress.com |
Great news! One last step: head over to your WordPress.com diff, D74096-code, and commit it. Thank you! |
Merged in rWPGIT07ee125049542037d912da58d21900a855c289bd ( r239514-wpcom ) |
In some cases that I haven't been able to duplicate yet, the hash could be an array. This fails to validate it in that case.
I tried to duplicate this by submitting an incomplete form a couple of times, but no luck.
Warning found from looking at logs:
Changes proposed in this Pull Request:
Jetpack product discussion
n/a
Does this pull request change what data or activity we track or use?
n/a
Testing instructions: