• Resolved Ludovic S. Clain

    (@ludovicsclain)


    Hi there ???
    I have just spoken with the support of the GoCardless plugin and it appears that BBQ Firewall is overzealous and causes 403 errors after purchase when redirecting to the site.
    Indeed, when I deactivate BBQ Firewall the GoCardless plugin works correctly.
    Here is a screenshot of the Webhook:
    https://markuphero.com/share/gvFLIAgZYgnLHB6G9IP7
    Thank you for your help!
    Warm regards,
    Ludovic

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Jeff Starr

    (@specialk)

    Hi Ludovic,

    In order to help investigate, I need to be able to recreate the 403 error. Can you let me know the steps to repeat it on default WordPress install?

    Thread Starter Ludovic S. Clain

    (@ludovicsclain)

    it’s a bit complicated, because GoCardless is a premium plugin, and you need a SandBox account at GoCardless too, maybe I can give you temporary access to my staging site?
    Also, I read about the BBQ Whitelist addon, I think I need to Whitelist something, but I don’t know what…

    Plugin Author Jeff Starr

    (@specialk)

    Yeah that’s really the ticket to resolving the issue: getting the URL that is blocked, and then use the whitelist plugin to ignore the offending pattern. We’re not allowed to log in to client sites, but if you can determine the URL, I can help you get set up with the whitelist plugin.

    Thread Starter Ludovic S. Clain

    (@ludovicsclain)

    Does the previous screenshot I left you help?
    https://markuphero.com/share/gvFLIAgZYgnLHB6G9IP7

    Maybe this URL
    https://staging.waomizik.re/wc-api/WC_Gateway_GoCardless/?request=webhook
    but I am not sure

    The HTTP ERROR 403 screenshot:
    https://markuphero.com/share/A2NcbkxY5dhna18NNyls/3

    Plugin Author Jeff Starr

    (@specialk)

    It might be the brackets (angle or square) that are included in the JSON data. But you would need to test it to be sure.

    Thread Starter Ludovic S. Clain

    (@ludovicsclain)

    Thanks. And so it could give what the content of the array for the BBQ Whitelist plugin please?

    Plugin Author Jeff Starr

    (@specialk)

    This should do it:

    $bbq_whitelist_query_string_items = array('(globals|request)(=|\[)');

    You can leave the other arrays empty.

    Thread Starter Ludovic S. Clain

    (@ludovicsclain)

    Great, it does the job, thank you very much for your precious time (I’m a big fan, I recently acquired some of your methods, and I love them)!

    Take care ??

    Plugin Author Jeff Starr

    (@specialk)

    Thank you, Ludovic ??

    Thread Starter Ludovic S. Clain

    (@ludovicsclain)

    Hey @specialk ??</img>?
    Just to let you know that I have some PHP warnings from bbq-whitelist plugin, It looks like an update to do for compatibility with PHP8.0 (but I’m not sure):
    Warning: foreach() argument must be of type array|object, null given in ~/wp-content/plugins/bbq-whitelist/bbq-whitelist.php on line 39
    Warning: foreach() argument must be of type array|object, null given in ~/wp-content/plugins/bbq-whitelist/bbq-whitelist.php on line 49
    Warning: foreach() argument must be of type array|object, null given in ~/wp-content/plugins/bbq-whitelist/bbq-whitelist.php on line 59
    Warning: foreach() argument must be of type array|object, null given in ~/wp-content/plugins/bbq-whitelist/bbq-whitelist.php on line 69
    Warning: foreach() argument must be of type array|object, null given in ~/wp-content/plugins/bbq-whitelist/bbq-whitelist.php on line 79

    Thank you for your help!
    Warm regards,
    Ludovic

    Plugin Author Jeff Starr

    (@specialk)

    Thanks for reporting, Ludovic. I’ve added to the list and will get ’em fixed up for the next plugin update. Cheers my friend.

    Plugin Author Jeff Starr

    (@specialk)

    Hey Ludovic, I just tested the whitelist plugin on PHP 8.0, 8.1, and 8.2. Could not repeat the described warnings. If you can provide the basic steps to repeat the issue on default WordPress, I will take a look and try to resolve asap. Thank you.

    Thread Starter Ludovic S. Clain

    (@ludovicsclain)

    Hey Jeff, I just reactivated my debug and nothing similar is now appear. Thank you for your concern, I think we can put it aside for the moment, false alert. All the best!

    Plugin Author Jeff Starr

    (@specialk)

    That is great Ludovic, cheers!

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Compatibility with GoCardless plugin (HTTP ERROR 403)’ is closed to new replies.