2.9.22 breaks honeypot

Yep, I confirm that. In fact I came here because of that. I’ll keep an eye on this issue.

Same issue for me. In my module i can see now te honey trap to leave blank. User should not see this. Following this topic and wait for a fix.

Honeypot is no longer in the Template Fields, however, it seems that it gets inserted automatically as the first field of the form. Concerning the fact that it gets exposed to the end user, I don’t have this issue, do you have the following line in your CSS ?

.hp-wrap {
    display: none;
}

Yes i have but issue are present
https://www.marcoborla.it/contatto-alternativo-alternative-contact-form/

Alright, it looks like the old Honeypot class was honeypot-wrap so add this line of CSS and you should be good:

.honeypot-wrap {
    display: none;
}

Maybe now i have added this seems is working.
No more visible to the user.

Hey all! We actually ninja’d a honeypot field into ALL forms from now on and removed it as a user-added field. If you added a honeypot before this patch, it is still there in addition to the new honeypot field. Names are randomized to help prevent spam as well!

wpnzach… This is great, but the problem is that the original honeypot that I put in is now exposed to the user.. which yes I can take it out… but the problem is that I maintain well over 50 wordpress sites and I would need to go through all the forms on all the sites and remove it.

Hey. This is something that was unintentionally borked with 2.9.22. Working on a fix now, and we’ll have a version 2.9.23 out very soon!

Thanks kstover. That approach is far better then going on every install and every form and remove each honeypot field.