identibyte / identibyte-for-contact-form-7 Goto Github PK

If the form validation fails with a disposable email, we have a hard-coded error message. There are two options here (and we can allow both):

• Allow the user to enter a custom message when Identibyte validation fails
• Allow user to choose the default "spam" message from CF7 (this should be the default).

Right now the user can enable Identibyte on a tag by adding the identibyte:true attribute to the tag. We should be able to add a checkbox option to CF7's form-tag generator that the user can just click.

Since Identibyte requires a token to make requests, this is an extra step the user has to take before Identibyte will work.

We need to show a persistent message in the admin panel if the user has this plugin enabled, but does not have a token saved.

Only a couple of things needed before we can submit to the WordPress directory:

• Add link to GPLv3 license file
• Add readme.txt
• Go through WordPress Developer Checklist
• Add screenshots
• Submit to WordPress Directory

Follow-up

• Add banner image for WP page

(Feedback Loop 1](#1 (comment))

First set of feedback tasks from the WordPress team

• Sanitize inputs (9c5d655)
• Check in logo image (a38f40c)
• Update readme abt 3rd party service (65d1545)
• Send new .zip file to WordPress team

In addition to email and email* fields, we can add filters to validate url and url* fields too.

Should just be a couple of lines, but locally I had issues with URL encoding the URL fields before sending them to Identibyte.

This will be useful for users in the EU, or similar, where they don't want to send a 3rd party service the full email for every user.

• Add an admin option to only send Identibyte the domain when checking emails.