that’s odd. Can you tell me the
- WordPress version
- Cf7 plugin version
- additional cf7 extensions
that you are using.
Thanks for picking this up.
– WP 6.2
– CF7 5.7.5.1
– CF7 Shortcode Enabler 1.1
– Divi CF7 1.3.4
– OTP by Email for CF7 1.1.2
ok. Will check this and revert.
OK. Maybe good to know that disabling the other two extensions makes no difference. Leaving WP 6.2 as the only suspect (?)
Ok, I just realised what may be the issue.
Have you setup an email field in your form? It needs an email field for the OTP to function. Insert one, and update the form and the OTP tab will show up.
I am just releasing v1.2 with the tab showing regardless of the any email field, but with a warning message when no email field is found. This will be less confusing for users.
I have also added an additional FAQ with an explanation as to how to use this plugin.
Ah, I have a hidden email field [hidden your-email readonly default:user_email], since I am not intending to use the plugin for email validation, but for request confirmation. I understand that I will have to unhide it.
Thanks.
If it is hidden, how do you get your visitor to fill in their email for verification?
I am trying to understand your specific case here, see if this is something to consider for future development of the plugin.
The user has already logged in and their email is known. The form concerns a request from the user and confirmation is required as an extra security measure.
Not showing the email address on the form is just cosmetic and not a big deal in this case. But another way for the plugin of checking if the email field exists (hidden or not) would make it perfect.
Ya. that kind of makes sense. I will incorporate the ability to use hidden fields in the next version.
Would you kindly leave a review when you have a minute to spare? The first one 🙂
