• Resolved ricardocosta

    (@madebyuh)


    Please check this GitHub ticket to understand the problem: https://github.com/Automattic/woocommerce-payments/issues/8500

    Response:

    With the aforementioned Brevo plugin specifically, we are finding that it is adding the following to the settings?_locale=user network response:

    <input type="hidden" class="ws_opt_in_nonce" name="ws_opt_in_nonce" value="[nonce]">
    

    Passing this value through the network response prevents the WooPayments pages from loading. You can test this without the Brevo integration installed by overriding the content of the settings?_local=user request…

    CleanShot 2024-04-01 at 15 12 39

    …and removing the <input> tag…

    CleanShot 2024-04-01 at 15 13 03

    From there, use CMD + S or CTRL + S to save your override changes, then refresh the page. It should load as expected.

    Alternatively, if the page is loading for you (e.g., you reverted to version 7.3.0 or the Brevo integration is deactivated) you can reproduce this issue by adding any HTML to the request. While <input> is added by the Brevo integration, other HTML tags like <p> and <em> will produce the same issues.

    What we suspect is happening here is that the 6a22e18 commit introduced the wocommerce_checkout_fields filter, which is triggering an opt-in via the Brevo integration.

    This is not an issue that can or will address in WooPayments. According to the WordPress developer Handbook:

    […] filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.

    While we could prevent that from our side by using output buffering before calling the filters, this could lead to other conflicts. As a result, it is best for the developers of the Brevo integration (or similar plugins that may be causing this issue) to resolve this.

    Many thanks for all of the reports, as they allowed us to isolate the cause! Given that this is a conflict with a third-party integration and that we will be unable to resolve it within WooPayments specifically, I will close this issue.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • PD

    (@peterdowney01)

    Can confirm this problem. Woopayments 7.4 update breaks when Brevo plugin is active.

    Plugin Support alexisbienayme

    (@alexisbienayme)

    Hi @madebyuh and @peterdowney01,

    We are aware of this issue and a fix will be made to the new version of the Brevo for Woocommerce plugin, which will be available in a few days.

    Don’t hesitate to let us know if you have any information.

    Best Regards,

    Alexis

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WooPayments Incompatible after version 7.4.0’ is closed to new replies.