• Resolved andyldex

    (@andyldex)


    Hi, we’ve just upgraded WordPress to 5.1 and all the plugins to their latest versions. We are now seeing 3 “configuration errors” on all our contact forms. We’re using a form like:

    <div style="text-align:center;">
    [text* name id:omni-name placeholder "Name"]
    [text* Postcode id:omni-postcode placeholder "Postcode"]
    [email* Email id:omni-email placeholder "Email address"]
    [tel Telephone id:omni-telephone placeholder "Telephone number"]
    [tel Mobile id:omni-mobile placeholder "Mobile number"]
    [textarea* Message id:omni-message placeholder "Your message"]
    [dynamichidden dynamicname id:dynamicname uneditable "CF7_bloginfo show='admin_email'"]
    [dynamichidden dynamicpurpose id:purpose "CF7_GET key='purpose'"]
    [submit class:btn class:standard-link "Get in touch"]
    </div>

    and it gives the error “Unavailable names (“name”) are used for form controls.”. Which ok, we can change name if need be, but it didn’t complain before.
    The bigger problem is on the mail page, it gives an error for having “To” set to [dynamicname] as “Invalid mailbox syntax used”. And for “From” we have it set as [name] <[Email]> and this gives the error ” Sender email address does not belong to the site domain”.

    We are on v2.0.2.1 of this plugin and v5.1.1 of Contact Form 7.
    Thanks for any assistance,

    Andy.

    • This topic was modified 7 years, 3 months ago by andyldex.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author sevenspark

    (@sevenspark)

    Hi Andy,

    These are just configuration notices from Contact Form 7. Basically it’s complaining that your field isn’t defined as an email address, and therefore might result in bad data in the form. As long as you’re guaranteeing that you’ll always be placing email addresses in those fields via the data you’re pulling dynamically, you can safely ignore those notices.

    Hope that helps

    Thread Starter andyldex

    (@andyldex)

    ok, thanks for clearing that up, appreciate the reply,

    Andy.

    • This reply was modified 7 years, 2 months ago by andyldex.
Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘syntax errors after upgrade to WP 5.1’ is closed to new replies.