Ryan

Thanks for the heads up. I’ve added this issue to my tracker, and will address it in the next update. Am a bit inundated with things at the moment, so I’m not 100% sure when that will get out, but asap. I’ll update this thread when I add it.

• This reply was modified 1 year, 7 months ago by Ryan.

So long as you’re using Contact Form 7, it should be compatible with any theme you use.

I don’t believe there’s any conflicts between the two. I have used both on sites before (for the same reason as you), and never had any problems.

I’ll dig into this in the next couple days. I’m not sure if it’s the same behaviour, but I did just notice a strange behaviour on one of my test sites. Perhaps something was changed in a recent update. I will update this thread (and the plugin) once I know more.

Hi @liri89 – are you using the timecheck feature? As the FAQ notes, there’s nothing magical about how a honeypot works. If/when bots are programmed to skip a honeypot field (either because it hasn’t been made to look like a regular field, or the bot has been programmed to look for key honeypot indicators), the honeypot method of spam stopping simply can’t work. That is why I added the additional timecheck feature. If that’s not enabled, give it a go. If it is enabled, unfortunately, you’ll have to go with stronger spam stopping (reCaptcha or something like that)

Yep! But I would recommend changing the honeypot-149 part to something more “tasty” to a spam bot… something like “email” or “website” or something like that. You can leave the “-149” bit to make sure it is unique from other fields in your form.

There are some additional features you can setup in the Honeypot settings page (Contact > Honeypot). I would recommend checking the “Enable Time Check” box.

Hi @werny – I’m not seeing the honeypot form element in the HTML of the CF7 form on that link. Have you inserted the honeypot tag into the form?

Hey @elixask – sorry about the slow reply, but, well… you get what you pay for ??

I took a look at your screenshots, and I would assume the issue has to do with whatever is causing W.JS to fail to load. I’m not sure what that JS file is for, but if it creates a JS error before the Honeypot plugin can add its button, that would cause the button to not appear.

If you can’t track down what W.JS is for, I would disable plugins (specifically anything to do with the editor) one by one and reload the form editor to see if the error still appears. You could also check other editor pages (e.g. the posts editor) and see if you also have the error there.

In Flamingo, is it storing them in the “Inbound Messages->Inbox” or “Inbound Messages->Spam” — it should be in the Spam section. You’ll definitely need the “Store Honeypot Value” enabled.

I don’t know of any conflicts with those plugins, and your versions are all good. The only thing I can think is maybe the caching plugin might be causing issues. You might want to disable that (or disable it on the page with the form) and see if anything changes.

Hi Elixa, when you visit the CF7 form editor page (where you create the CF7 form), can you right-click and select something like “Inspector”, you should then see a tab in the inspector that says “console”, this will typically reveal any errors (specifically Javascript errors) that may be causing conflicts. If there is an error before Honeypot runs, it might break things.

Hey Damien, that does seem strange. Are you comfortable with using your browser’s “inspector” function? If so, you can inspect the HTML code, and then edit a value for the honeypot field and try to submit. It should reject it. I just installed the exact honeypot shortcode you’re using on my site and tested and it is working. I’ll let it run for a while and see if it continues to block spam in the wild as well.

Just to confirm, are you running the latest versions of WordPress, CF7 and the Honeypot plugin?

I would try renaming the honeypot to something other than “telephone”, as that’s rarely a spam-targeted field. Try URL or website or email or something along those lines. You may also want to play with the timecheck setting. Set it a bit higher. If that doesn’t improve things, there’s a chance that the spam bots hitting your site are too advanced (or aren’t bots) and thus the honeypot can’t stop them. You should also be able to confirm that it’s stopping things using the basic analytic at the bottom of the Honeypot settings page. It reads something like “Honeypot has stopped ### spam submissions since ____ (date of install)”. As an example, on my main site, it has stopped 960 spam submissions since last month.

Hi @noquest – thanks again for bringing this to my attention. I’ve tracked down the bug and squashed it. I’ve pushed out an update, v. 2.1.1. Please let me know if you continue to have any trouble, or notice any other odd behaviour.

Can confirm, I also see this bug. Looking into it further, will update once I’ve squashed it. Thanks for bringing it to my attention @noquest

Hi @noquest – very strange indeed. Just to be clear, so I can repeat steps and test:

1. You have a number of plugins that are installed but deactivated, including Honeypot for CF7.
2. You try to bulk activate X number of plugins (including/not including honeypot?)
3. You receive an error page that says “the link you are following has expired”

Is that right?