Plugin breaks checkout page if using blocks

  • Resolved geea

    (@geea)


    1 week, 3 days ago

    If the checkout page is built using blocks and not the shortcode, the checkout page stops working (clicking on the Place Order button does nothing) and the console shows the following errors:


    GET /wp-json/wp/v2/users/me?context=edit&_locale=user 401 (Unauthorized)

    Uncaught (in promise) 
    {code: 'rest_not_logged_in', message: 'You are not currently logged in.', data: {…}}

    I’ve tested this with a default theme and all plugins deactivated, the error disappears when either the Checkout Field editor is removed or when we switch to a checkout page that uses the shortcode, not the blocks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Elena

    (@elenathemehigh)

    Could you please confirm if you’re using the latest versions of both WordPress and WooCommerce?

    Also, could you please confirm whether you have deleted any default WooCommerce fields using our plugin?

    Please note that it is recommended not to remove or override the default WooCommerce fields as it may lead to unexpected errors on your website.

    Based on the error message you provided, we believe that it might be related to the below points.

    Check REST API Authentication

    • The blocks-based checkout might rely on REST API endpoints that require proper authentication. Ensure that:
    • The REST API is enabled and functioning correctly. You can test this by visiting?/wp-json/?on your site (e.g.,?https://yoursite.com/wp-json/).
    • Nonce or session-based authentication is working correctly for logged-in users.

      Thank you!
    Thread Starter geea

    (@geea)

    Hi Elena,

    Thanks for your reply. Yes, we use the latest versions of everything and REST API is working ok.

    We did disable some of the required WC fields: billing address, country, and postcode by unchecking both Required and Enabled, which the plugin allows us to do.

    Anyway, we’ve switched to the shortcode page which works, I was just letting you know about this issue in case you want to address it in a future update.

    Plugin Support Elena

    (@elenathemehigh)

    Hi @geea

    We appreciate you sharing that information with us.

    As we mentioned in our previous update, it is recommended not to remove or override the default WooCommerce fields as it may lead to unexpected errors on your website and we believe it might be the cause of the issue.

    That said, we’re still looking into this to see if there are any other factors contributing to the issue.

    We’re happy to hear that switching to the classic checkout page has resolved the issue for now.

    Thank you!

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