• I used this on two high traffic sites alongside Akismet. The fully automatic list is too severe and despite a number of authors having dozens of previously approved comments their comments were blacklisted.

    Somehow the “123 approved” field was being over ridden in one case. That person was also a site editor which was also somehow being missed. The same thing happened to other editors. I don’t think registered users ( especially at editor level) should be blocked like this.

    It also blocked some external commenters / but in many cases they had a few previous comments approved. Blocking the registered users is the part which should never happen.

    I have no doubt this works but there is clearly some settings which need to be fine tuned.

Viewing 1 replies (of 1 total)
  • Plugin Author Grant Hutchinson

    (@grantsplorp)

    Hi Jason.

    Sorry for taking so long to reply to your original comment. I would be curious to know what content was contained in the comments which were being blocked. I have never used Akismet on a site where I already have the blacklist in place, so I’m wondering if that’d where some of the comment stomping is occurring.

    As for editors and pre-approved commenters being exceptions to the blacklist, that’s a function of WordPress, not the plugin. Regardless of your user status, if something in the blacklist is matched, that comment is bombed.

    Keep in mind that I am constantly optimizing and updating the master blacklist. It could very well be that there were terms in the July 2014 release of the blacklist which could have been commonly used phrases within the context of your sites.

    If you’d be willing, I’d love to have to test out the blacklist again (with or without the help of the plugin) and pass along any false positives to me.

Viewing 1 replies (of 1 total)
  • The topic ‘Overkill in the extreme’ is closed to new replies.