W3C Validation workaround failed

  • Resolved paulligasphotography

    (@paulligasphotography)


    3 years, 10 months ago

    My contact form failed with the default honeypot settings, and I discovered the word “nope” when inspecting the field in my browser. that led me to the W3C Validation workaround thread, but checking that field also didn’t work. What worked for me was manually editing the php to change the word “nope” to “no”. Now the contact form works. I don’t know if that’s broken the honeypot or not. Still, no worse than before if it has. I now have to make sure the plugin doesn’t auto update, though.

    Is there something else i could do instead?

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi, you definitely shouldn’t modify the PHP directly. If you must change the HTML output of the field, you should use the filters, as this will allow you to upgrade the plugin without losing your changes/modifications. More on that here.

    That said, the validautocomplete:true flag, when added to the honeypot shortcode in the CF7 form creator appears to allow the form to pass W3C validation. (tested with most recent version of the plugin here)

    If your field is still setting autocomplete=”nope” after setting the flag in the shortcode as above, can you please copy your shortcode here, so I can test/review?

    Thread Starter paulligasphotography

    (@paulligasphotography)

    Hi Ryan. Thanks for the reply. I tried it again, after reverting the php to the original, but this time I changed the location of the honeypot shortcode in the contact form – higher up and in between name/email fields instead of just above ‘Send’, and this time it appears to have worked in my test. I’ll keep an eye on it, but if I have another issue I’ll open another post. Thanks again.

    P

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘W3C Validation workaround failed’ is closed to new replies.