Hi @dariyar
“CSS Hack” does not mean there is CSS in the comment and therefore the comment is marked as spam, it means that our “honeypot” was filled out. This typically means that something was going wrong (Antispam Bee was not able to add the honeypot correctly, for example because Jetpack Comments is active or another incompatible plugin or something similar)
See: https://antispambee.pluginkollektiv.org/documentation/#suspicion-of-spam-detection
This spam reason was re-named to “Honeypot” long ago with version 2.8.0 (https://github.com/pluginkollektiv/antispam-bee/commit/c38050d8b854ad8ffcf7851b5b21b50d78cd9176). So I would strongly recommend updating the plugin to the recent version first.
If the problem persists after the update, please share your active plugins, active theme, your website URL and your settings, so that we can check was is going wrong on your site.
All the best
Torsten
Oh, thank you, I’ve understood my problem. There is a custom form for comments on this site and honeyspot doesn’t appear here. Can I add honeyspot manualy in form or with shortcode for example? Or shoud I change form to default?
Hi @dariyar
this depends on how the custom form is built. We use a regular expression to add our honeypot. For highly modified forms, this could lead to a failing match.
Using the default form would solve this problem.
If you are familiar with PHP and regular expression, you can look at our code and try to make it work again manually:
https://github.com/pluginkollektiv/antispam-bee/blob/master/antispam_bee.php#L1270-L1312
Or you try to add the honeypot manually. But you need to build this yourself. This is a tutorial to build an ajaxified comment form which can help you to build this (in German, but Google Translate will help you):
https://torstenlandsiedel.de/2020/10/04/ajaxifizierte-kommentare-und-antispam-bee/
Hope this helps! If you still need help and you can share your custom form code, then please paste it here and I will try to make it work for you again!
All the best,
Torsten
Thx for reply.
I have next code on the site. Can I add honeypot manualy?
<form action="<?php echo get_option('siteurl'); ?>/wp-comments-post.php" id="commentform" method="post">
<div class="product_form_inputs">
<input required placeholder="Name" name="author" id="author" type="text">
<input required placeholder="Email" name="email" id="email" type="text">
</div>
<div class="product_form_textarea">
<textarea required placeholder="Review" name="comment" id="comment"></textarea>
</div>
<div class="product_form_btn-rate">
<?php comm_rating_rating_field (); ?>
<input class="product_form_btn" type="submit" value="Send">
</div>
<?php comment_id_fields(); do_action('comment_form', get_the_ID()); ?>
</form>
I decided to replace this form with the standart form and problem has dissapeared.
Thank you once again for the feedback!
It should have worked. Tried our regex on this form and it worked:
https://regex101.com/r/NzCLR4/1
Since version 2.10.0 we have an option to switch between whole markup (via output buffering) and using a filter:
“Check complete site markup for comment forms”
For others who find this thread: You can try to enable/disable this option. Maybe it helps.
If not please open another support thread and we will try to help you!
