• Dear all, we enjoy MailPoet, but we cannot use it on the new WooCommerce block checkout.

    After activating MailPoet: WooCommerce: Opt-in on checkout page (“Opt-in auf Bezahlseite”), customers see payment options in checkout, but when trying to complete checkout (everything is correctly filled in, including valid credit card payment data) by clicking on the complete checkout button (“kostenpflichtig bestellen”), the checkout process fails with a fatal 400 error due to invalid parameter: extensions.

    The customers see a red circle with white exclamation mark icon and an error message (localized in German: “extensions > mailpoet ist nicht vom Typ object.” (extensions > mailpoet is not of type object). The error message is displayed as a dismissable notice (.woocommerce-error components-notice.is-dismissible .components-notice__content) but the error prevents the customers to complete the checkout.

    After deactivating the checkout opt-in feature, users can complete the checkout successfully.

    WordPress 6.1.1
    PHP 7.4.33
    MailPoet 4.0.1
    WooCommerce 7.1.0
    WooCommerce Blocks 9.0.0
    WooCommerce Payments 5.0.3
    WooCommerce Shipping & Tax 2.0.0
    Germanized für WooCommerce 3.11.1
    Germanized für WooCommerce Pro 3.6.2

    Request Status:
    /wp-json/wc/store/v1/checkout?_locale=user
    Failed to load resource: the server responded with a status of 400 ()

    Response Details:

    
    {"code":"rest_invalid_param","message":"Ung\u00fcltige(r) Parameter: extensions","data":{"status":400,"params":{"extensions":"extensions > mailpoet ist nicht vom Typ object."},"details":{"extensions":{"code":"rest_invalid_type","message":"extensions > mailpoet ist nicht vom Typ object.","data":{"param":"extensions > mailpoet"}}}}}
    

    Request Payload:

    
    {"billing_address":{"first_name":"John","last_name":"Doe","company":"","address_1":"Teststr. 123","address_2":"II (Vorderhaus)","city":"Berlin","state":"","postcode":"12043","country":"DE","email":"[email protected]","phone":""},"customer_note":"Testbestellung wegen Zahlungsarten vs. Mailpoet opt-in","create_account":false,"payment_method":"woocommerce_payments","payment_data":[{"key":"paymentMethod","value":"woocommerce_payments"},{"key":"wc_payment_intent_id","value":"pi_3M8iYfFmV1RD0GLh14yzYImX"},{"key":"wcpay_selected_upe_payment_type","value":"card"},{"key":"wc-woocommerce_payments-new-payment-method","value":false}],"extensions":{},"shipping_address":{"first_name":"John","last_name":"Doe","company":"","address_1":"Teststr. 123","address_2":"II (Vorderhaus)","city":"Berlin","state":"","postcode":"12043","country":"DE","phone":""}}
    
Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Ingo Steinke (openmindculture)

    (@openmindculture)

    Is this error supposed to be fixed in MailPoet 4.1.1 / WooCommerce 7.1.1?
    Is it safe to try again?

    Thread Starter Ingo Steinke (openmindculture)

    (@openmindculture)

    Before crashing my customer’s WooCommerce shop again, like I asked in the support post, is it safe to use after the update now? Because the reported versions were definitely NOT COMPATIBLE in reality, as they resulted in a fatal error message caused by MailPoet, which prevented our customers to proceed with the checkout!

    Is this error supposed to be fixed in MailPoet 4.1.1 / WooCommerce 7.1.1?
    Is it safe to try again?

    Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    Hey there!

    Thanks for contacting MailPoet, happy to help.

    MailPoet 4.3.0 should be good to go.

    Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

    Thread Starter Ingo Steinke (openmindculture)

    (@openmindculture)

    Currently, the latest update stopped the error, but MailPoet did not show in WooCommerce block checkout anymore, it seems.

    We will try again after reverting to classic checkout and update this issue.

    I will probably recommend my customer to switch to MailChimp anyway.

    Thread Starter Ingo Steinke (openmindculture)

    (@openmindculture)

    Tried again with WooCommerce 7.3.0, Classic Checkout, MailPoet 4.6.1, activated MailPoet: Settings: WooCommerce: “Opt-in auf Bezahlseite” (opt-in on checkout page): no error, but still no opt-in checkbox either.

    Thread Starter Ingo Steinke (openmindculture)

    (@openmindculture)

    MailPoet 4.6.2
    WooCommerce 7.4.0
    WooCommerce Blocks 9.6.1

    and finally it works!

    Probably thanks to MailPoet’s “fix potential conflict between newsletter extensions on the checkout page” which also works in our classic checkout at least.

    Thanks for the fix!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Opt-in causes WooCommerce Checkout fatal error 400 invalid parameter extensions’ is closed to new replies.