Oops, something went wrong… and 422 status

  • Resolved myso

    (@myso182)


    7 years, 6 months ago

    Hello,

    I am not able to place order when using your latest version 2.2.0. It is not possible to finish checkout process and I am getting message: Oops, something went wrong. Please try a different payment method.

    When looking at console there is a 442 status for POST request. This is same for both Sandbox and Production environments:

    Failed to load resource: the server responded with a status of 422 (Unprocessable Entity)

    Please see screenshot for more details: https://imgur.com/lRGLblx

    For now I restored version 2.1.3 and there is everything OK and we are able to place orders and make successful payments.

    Thanks in advance for your reply.

    Michal

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Hannah S.L.

    (@fernashes)

    Automattic Happiness Engineer

    7 years, 6 months ago

    Hey there!

    To help you troubleshoot this, we’ll need to take a closer look at your site.

    Could you please contact us at WooCommerce.com > My Account > Tickets? You may need to create an account. We will be able to help you further there.

    matteth

    (@matteth)

    7 years, 6 months ago

    We’re having the same issue as others here and have lost sales for a few days until reverting to the previous version. @fernashes, this issue has been marked as resolved when you moved it into private support. Is it really resolved?

    Thread Starter myso

    (@myso182)

    7 years, 6 months ago

    Hello Hannah & Mats,

    @fernashes – thanks for your reply. Ticket for this issue is now created.

    @matteth – I think this was marked as resolved because they are not going to discuss it here, but on their extra forum/chat located on WooCommerce website. Ticket for this issue is now open, it was surprise for me when support guy told me that issue was not already reported. Plugin has 80,000+ active installations :-O… I can confirm it is 100% problem with plugin, because I was able to recreate error on fresh WordPress install with default Twenty Seventeen theme and only WooCommerce and Braintree plugins activated.

    Michal

    Plugin Support Hannah S.L.

    (@fernashes)

    Automattic Happiness Engineer

    7 years, 6 months ago

    Hey there,

    I think this was marked as resolved because they are not going to discuss it here, but on their extra forum/chat located on WooCommerce website

    That’s exactly it – we don’t want to have the same discussion in two places, as details get lost. That’s also why we recommend each user have their own thread, so that we can handle them separately.

    matteth

    (@matteth)

    7 years, 6 months ago

    @fernashes Having open support for an open source plugin in an open forum saves everyone time and effort, avoiding duplication.

    Plugin Support Hannah S.L.

    (@fernashes)

    Automattic Happiness Engineer

    7 years, 6 months ago

    Hey there,

    Indeed – and in most cases, it’s best to troubleshoot publicly so that others can learn from it. However, with this error, we’re going to be asking about setup, logs, etc., and it’s easier to do that in a place where privacy isn’t a potential issue.

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

The topic ‘Oops, something went wrong… and 422 status’ is closed to new replies.

Tags