Support » Plugin: Block Bad Bots and Stop Bad Bots Crawlers and Spiders and Anti Spam Protection » Its a terrible Plugin that Crashed my WordPress

  • Kelvin

    (@myinternet11)


    I bought the premium version of the plugin in April 2022.

    Its a terrible plugin although support is responsive but not helpful.

    In May 2022, I noticed that my website(s) have started to have loading issues and blocking legitimate traffic including mine.

    Bill Minozzi from support listed plugin conflict as one of the reasons, pointing to Jetpack and Sucuri. Basically he is saying Jetpack and Sucuri should fix the conflict (if any) with StopBadBots?

    So I reduced the protection of StopBadBots and the issue went to minimum although its still blocking legitimate traffic.

    On 12-Oct, an automated email from WordPress says that one of my site has crashed. Below is a partial error detail:
    “Howdy!

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, StopBadBots.`

    An error of type E_ERROR was caused in line 2931 of the file /home/xxx/wp-content/plugins/stopbadbots/functions/functions.php. Error message: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /home/xxx/wp-content/plugins/stopbadbots/functions/functions.php:293”

    I believe the error was then fixed with a plugin update 2 days later but I stopped using the plugin since it crashed the site.

    This is a real user experience.

Viewing 1 replies (of 1 total)
  • Plugin Author sminozzi

    (@sminozzi)

    Hi Kelvin,

    Use our support page for premium plugin. Not fair with WordPress post here.

    Not good idea put to work together many security plugins. Take one and left other.

    This error happens when contact our server for upgrade and doesn’t affect your users. Not a big deal. Anyway, update your plugin to the last version (7.23) and this error will vanish.

    Please, change this review to 5 stars.

    Cheers,
    Bill

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this review.