• Resolved gwm73

    (@gwm73)


    I thought the installation was OK but then noticed this error email, can you help please? Thanks.

    Error Details

    =============

    An error of type E_ERROR was caused in line 123 of the file /srv/htdocs/wp-content/plugins/botblocker-security/includes/botblocker/traits/class-botblocker-cookie-trait.php. Error message: Uncaught ValueError: setcookie(): Argument #1 ($name) must not be empty in /srv/htdocs/wp-content/plugins/botblocker-security/includes/botblocker/traits/class-botblocker-cookie-trait.php:123

    Stack trace:

    #0 /srv/htdocs/wp-content/plugins/botblocker-security/includes/botblocker/traits/class-botblocker-cookie-trait.php(123): setcookie('', '', Array)

    #1 /srv/htdocs/wp-content/plugins/botblocker-security/includes/botblocker/traits/class-botblocker-cookie-trait.php(70): BotBlocker->set_cookie('', '', 1765637337, false, 'Lax')

    #2 /srv/htdocs/wp-content/plugins/botblocker-security/includes/botblocker/traits/class-botblocker-visitor-trait.php(72): BotBlocker->delete_cookie('')

    #3 /srv/htdocs/wp-content/plugins/botblocker-security/includes/botblocker/class-botblocker.php(89): BotBlocker->process_cookies()

    #4 /srv/htdocs/wp-content/plugins/botblocker-security/includes/botblocker/class-botblocker.php(72): BotBlocker->run()

    #5 /srv/htdocs/wp-content/plugins/botblocker-security/includes/class-cyber-secure-botblocker.php(66): BotBlocker->initialize()

    #6 /srv/htdocs/wp-content/plugins/botblocker-security/botblocker-security.php(181): Cyber_Secure_Botblocker->run()

    #7 /wordpress/core/6.9/wp-includes/class-wp-hook.php(341): bbcs_run_botblocker_shield('')

    #8 /wordpress/core/6.9/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters('', Array)

    #9 /wordpress/core/6.9/wp-includes/plugin.php(522): WP_Hook->do_action(Array)

    #10 /wordpress/core/6.9/wp-settings.php(593): do_action('plugins_loaded')

    #11 /srv/htdocs/wp-config.php(94): require_once('/wordpress/core...')

    #12 /wordpress/core/6.9/wp-load.php(55): require_once('/srv/htdocs/wp-...')

    #13 /wordpress/core/6.9/wp-admin/admin.php(35): require_once('/wordpress/core...')

    #14 /wordpress/core/6.9/wp-admin/index.php(10): require_once('/wordpress/core...')

    #15 {main}

      thrown
    • This topic was modified 1 month ago by gwm73.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Yevhen Leonidov

    (@globusstudio)

    Thank you for letting us know!

    The good news is that this issue does not affect the security of your website in any way. The only impact is that, in some cases, a user whose cookies were not set correctly may be asked to pass our captcha verification again.

    We are releasing a fix for this today that fully resolves the issue.
    Please update the plugin as soon as the update is available.

    Thank you very much for your feedback and for helping us improve BotBlocker.

    Thread Starter gwm73

    (@gwm73)

    Thanks for the swift response, really appreciated. That is exactly the issue that some of my visitors have experienced. Uses were completing the challenge at the checkout but were sent round in a loop so the order could not be completed. Hope the update fixes the issue.

    Plugin Author Yevhen Leonidov

    (@globusstudio)

    Thank you for your detailed description of the situation.

    To avoid getting stuck on checkout in WooCommerce, please do the following.

    1. Add and enable (Allow) these paths (BotBlocker – Rules – Paths).

    For a standard WooCommerce site, we recommend allowing:

    • /checkout/
    • /cart/
    • /my-account/
    • /?wc-ajax=

    If you are using WooCommerce Blocks (new checkout), additionally:

    • /wp-json/wc/store/

    In upcoming versions, we will automatically create rules when installing WooCommerce on a site.

    2. Be sure to enable the rules

    Please note: the paths currently on the list are not active – they are highlighted in red. They need to be enabled so that they turn green and actually work.

    3. It’s safe

    Adding these paths does not compromise the security of the site.

    BotBlocker only allows verified users to pass through them so that sessions, cookies, and order processing work correctly.

    4. Plugin update (Cookie issue)

    We have also released BotBlocker version 1.6.8, which fixes a cookie issue.

    Please update to the latest version.

    We would appreciate your feedback after updating and enabling these rules – did it completely solve the problem?

    Thread Starter gwm73

    (@gwm73)

    Thanks again for the advice. Plugin updates and rules implemented. I will let you know if I have any further issues, none to report as yet.

    Thread Starter gwm73

    (@gwm73)

    Everything is running well now thank you. Can I ask does Bitblocker block Woocommerce Rest API requests? If it does is there a white list feature to allow requests from specific URL’s? I have an API set up with my shipping company that automatically updates an order status and then sends a tracking order email from mt Woocommerce store when a shipping label is printed on the shippers system. Since I installed Bitblocker this isn’t happening. Any assistance greatly appreciated.

    Plugin Author Yevhen Leonidov

    (@globusstudio)

    Yes BotBlocker can block WooCommerce REST API requests, and yes, it has a whitelist mechanism that allows you to safely enable them only for your shipping provider, without opening the API publicly.

    Step 1. Temporarily allow the required API path

    Add the required WooCommerce API path to Paths and mark it as Allowed.

    Typical: /wp-json/wc/v3/

    Step 2. Trigger real API traffic

    Do one of the following:

    • Place a real test order, or
    • Let the shipping company print a label so their system calls your WooCommerce API

    This will generate real requests that BotBlocker can log.

    Step 3. Analyze the Full Log

    Go to Full Log and search for requests hitting the allowed API path.

    Now check how the shipping company can be identified. Most commonly it will be one of these:

    • User-Agent (best and most reliable)
    • IP address (acceptable, but less reliable, dynamic? or range?)
    • PTR / reverse DNS (usually very reliable for large logistics providers)

    Step 4. Create a permanent allow rule directly from the log

    From the log entry, create a rule that:

    • Allows requests by User-Agent (ideal), or
    • Allows requests by PTR, or
    • Allows requests by IP (fallback option)

    Set the expiration date far in the future (for example, +10 years — effectively permanent).

    Step 5. Disable the open API path

    After the identification rule is active:

    • Disable or remove the previously allowed API path

    Result:

    • WooCommerce REST API remains protected
    • Only your shipping company can access it
    • No public or anonymous API access
    • Order status updates and tracking emails will work again
    Thread Starter gwm73

    (@gwm73)

    Thanks again for the prompt and excellent support Yevhen. Rules implemented and all working just fine ;c)

    Plugin Author Yevhen Leonidov

    (@globusstudio)

    We’re happy to help! Contact us!

Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.