Hi @alexanderhammerschmied,
I guess you mean this plugin? https://thrivethemes.com/comments/
Unfortunately, I do not know this plugin and as it is a premium plugin, I can’t have a quick look into it. From what I see, they do quite a lot on the comment form and change the defaults. So it seems to me, they are also changing the name-attribute of the comment textarea.
This means, Antispam Bee and Thrive do not share a common ground on which they could work together right now, I am afraid of. In our code, we rely on the name attribute to do some of our work: https://github.com/pluginkollektiv/antispam-bee/blob/master/antispam_bee.php#L1248
I also digged a bit deeper into your HTML source, I think even if Thrive would use the default name for comments, we probably still wouldn’t be able to work with it, as there is a lot of javascript templating involved.
So, to me it seems, these to plugins cant work together. I am very sorry :/
Hi @websupporter,
thank you for this quick, clear answer!
That’s very helpful.
Now i understand what’s going on!
I’ll ask at thrivethemes what there tactics is going to be with the comment system and let you know!
Thank you very much!
Best,
Alex
@alexanderhammerschmied –> have you got a response from Thrivethemes? I asked them about this, and all I got was a link to this page: https://thrivethemes.com/tkb_item/how-are-bugs-and-feature-requests-logged-and-released/
Not really helpful 🙂
You don’t need AntispamBee when running Thrive Comments. This plugin already has is a built-in antispam filter and the way that Thrive Comments is designed, it doesn’t attract bots or spammers just looking to get a backlink. Since installing Thrive Comments, I’ve yet to receive a single bot-automated comment and anyone who tries to include a link along with their comment automatically gets flagged for moderation by the plugin.
Sources:
https://thetechreviewer.com/software/thrive-comments-review/
https://thrivethemes.com/comments/
