If the 'Protect all forms with Honeypot' checkbox is checked, the 'Honeypot Enabled Forms' fieldset should simply be invisible. This would help with UX where an admin might wonder why Honeypot is still enabled on a form that's not checked in the Honeypot Enabled Forms section...

Comments

john_b’s picture

john_b commented

This occurred to me too.

The module now does everything it should, and I cannot myself see any advantage in adding the extra facility to enable it on a per form basis, as no form should be hit more than once every 5 seconds, or should be usable by an automated bot of any kind, ever. But maybe others who are running complex sites will find that feature useful? At most I would have thought the facility to enable invisible field, and time stamp protection independently of one another, would be enough.

barrett’s picture

barrett commented

I agree with John_B regarding the need to be able to split the time and hidden field protections. I know this is available via code, but to be able to do it in the interface would be great.

Until that's in place, I think the ability to use honey on a form by form basis is necessary.

geerlingguy’s picture

geerlingguy commented
Assigned: Unassigned » geerlingguy
Status: Active » Fixed

A quick glance at the form api #states documentation helped to finish off this particular issue. Please open up follow-up issues to discuss what forms should be able to be configured individually (for now, I'm thinking at least node-type forms, webforms, and maybe a few other system forms).

geerlingguy’s picture

geerlingguy commented
Status: Fixed » Closed (fixed)

Closing out some old issues.