CF7 Honeypot 1.7 – Rapid updates, PHP errors, compatibility, oh my!

  • Ryan

    (@daobydesign)


    9 years, 5 months ago

    Just a quick note to apologize for the rapid succession of updates over the last few days. There were a few significant changes with CF7 in the most recent update, and that caused a few hiccups with the Honeypot plugin.

    All of this should be sorted now in the latest version (1.7) of this plugin. It is compatible with CF7 4.2, and backwards compatible to at least CF7 3.6.

    I’ve also added a new feature that allows you to disable a usability message that is, by default, outputted beside the honeypot field. This message (“Please leave this field empty.”) is displayed in case the field becomes visible to the end user for some reason — such as in the case of screen readers and other usability situations. It is the default option to have this enabled, and while it’s not recommended to remove it, should you desire to, you now can.

    If you have any troubles with the update or the new feature, please let me know in this thread.

    https://www.ads-software.com/plugins/contact-form-7-honeypot/

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

  • Suggestions:

    1. Make this message “configurable” with own string/html, empty string = no message.

    2. Add options which allow disabling/configuring the inline style="xxx" and tab-index="-1" etc. which can be used by bots to find the honeypot field.

    A more general approach for this (and to avoid user confusion if these options can be set via CF7 backend) could be a filter for the <span> and <input> tags which allows filtering (adding/removing) all attributes, so a programmer could do something like this in function.php, untested pseudo-code:

    function my_cf7_honey_args( $attr, $what ) {
	switch ( $what) {
	case 'span':
		$attr['style'] = '';
		$attr['id'] = 'my_new_attribute_id';
		break;
	case 'input':
		$attr['tab-index'] = '';
		$attr['type'] = 'email';
		break;
	case 'msg':
		$attr['html'] = 'Here is <em>my</em> message'; // empty disables msg span
		$attr['class'] = '';
		break;
	}
	return $attr;
}
add_filter( 'cf7_honey_args', 'my_cf7_honey_args', 10, 2 );

    If you need any help how to use the filter within the plugin, let me know, I can supply the relevant code…

    Thread Starter Ryan

    (@daobydesign)

    Good suggestions. Actually, there is a filter for modifying the output already, see the end of the Installation instructions.

    I considered adding additional string customization for the useability message, but decided simplicity was best — and if additional customization was needed, the filter above could be used.

    Allyson

    (@allysonsouza)

    After the update, my honeypot field became visible.

    Thread Starter Ryan

    (@daobydesign)

    What versions of WordPress, CF7 and CF7 Honeypot are you using?

    Allyson

    (@allysonsouza)

    WordPress 4.3.1
    CF7 4.3
    CF7 Honeypot 1.7

    Thread Starter Ryan

    (@daobydesign)

    Strange. Can’t think of what would cause that. Have you inspected the source generated in the form’s HTML? Do you have a link I could see? If you don’t want to make it public, feel free to e-mail me at: ryan at nocean dot ca

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘CF7 Honeypot 1.7 – Rapid updates, PHP errors, compatibility, oh my!’ is closed to new replies.