• This topic was discussed before here. CF7 throws an error if [email] is used in the email field. While I perfectly understand the idea, it is really not realistic at all. What else would I put in email 2 that goes to the user? There is nothing I can do about it, since this field HAS to fetch the address dynamically. I could supress the validation like so:

    define('WPCF7_VALIDATE_CONFIGURATION', false);

    However, this would remove ALL validation which is not exactly a good idea.

    A dirty workaround would be to activate the Google Recaptcha integration and to remove it like so:

    add_action('wp_print_scripts', 'deregister_google_captcha', 100);
    function deregister_google_captcha()
    {
        wp_dequeue_script('google-invisible-recaptcha');
        wp_dequeue_script('google-recaptcha');
        wp_dequeue_script('wpcf7-recaptcha');
    }

    It works, but it is putting the cart before the horse.

    What we need is a simple checkout for removing this specific validation. In Europa, Google Recaptcha is simply not an option anymore.

    • This topic was modified 11 months, 3 weeks ago by cutu234.
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Unsafe email configuration’ is closed to new replies.