Hi @nicopaleo,
I am still digging in the dark, but if it is not related to the caching, we could try, if this helps:
<?php
/**
* Plugin Name: Antispam Bee - Secret Generator
* Description: Generate your own Antispam Bee secrets.
**/
/**
* Generates a new name for the textarea.
*
* @param string $secret The secret.
* @return string
**/
function ab_get_static_name_secret( $secret ) {
return '43fgsg-daf';
}
/**
* Generates a new id for the textarea.
*
* @param string $secret The secret.
* @return string
**/
function ab_get_static_id_secret( $secret ) {
return '78dfmgdxdw';
}
add_filter( 'ab_get_secret_name_for_post', 'ab_get_static_name_secret' );
add_filter( 'ab_get_secret_id_for_post', 'ab_get_static_id_secret' );
This is an add on plugin for Antispam Bee I’ve just developed. It’s job is to take care about some naming in the Honeypot system. The problem you describe looks like Antispam Bee is not able to detect the comments text before passing it to the WordPress comment system. With this plugin, we make sure, we have a fixed key for this text.
What to do?
* Activate Antispam Bee
* Activate the plugin above
* Flush the cache
I do not really know, if this will work in the end, because as I said, I am still digging in the dark. But please tell me, if it works or not, because if it does, we have quite well localized the problem ( & fixed it for you) and can ship a better version the next time.
Thank you ??
