Smart Blocking is too restricitve

  • Resolved samcaughley

    (@samcaughley)


    4 months, 2 weeks ago

    We’ve been using the HTTP request logging, and have identified a couple of key plugins that are making too many requests. We only want to block the requests for these specific plugins, which can only be done using the custom rules. However, enabling the smart block breaks our site, and prevents whole pages from ever loading (in particular, if we’re running certain plugins at the same time then we can’t even load the HTTP Requests Manager settings page to switch the Smart Blocking off). Is there anyway we can either only use the custom blocking rules, or that we can adjust the Smart Blocking restrictions (without having to go into the plugin files themselves)?

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

    (@veppa)

    It seems like some plugins should be always allowed.

    Can you please try following setup.

    Say for example:

    a1, a2 — plugins or theme break your website when they are blocked or limited by smart block.

    b1, b2 — plugins that do not effect WordPress when they are blocked. And you want to block them.

    1. First create rule that will allow “a1” and “a2” plugins “always” “everywhere”.
    2. Then switch to “smart block”.
      • Test if website works. Then block “b1” and “b2” plugins.
      • If website crashes then it means there is some other plugin “a3” that should always be “allow”ed. This “a3” also can be one of “b1” or “b2” plugins.

    In other words if your website crashes/breaks when blocked eather by “smart block” or by “custom rule” then some plugin needs to be “always allowed” via “custom rule”. You can find that plugin by guessing it and allowing. Then switching to “smart block”.

    Some premium plugin or theme that checks for license might need to be always allowed. So allow them first before switching to “smart block”.

    Hope this helps.

    Please let me know how it goes.

    Regards.

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