• Hi, after the update this morning to 2.3.9 we couldn’t open one specific order; it resulted in a critical error. (like the screenshot in previous support ticket – only title text field is visible).

    Other orders are okay to open.

    Solution: back to previous version.

    The only ‘strange’ difference between our orders, the bPost status of that specific order is: UNKNOWN status. The same status is seen on both bpost plugin versions.

    Any idea?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Antidot developer

    (@antidot-dev)

    Hi,

    The solution is to rollback to 2.3.8, or to 2.3.7?
    In your SHM, what is the status of the order?

    Have you some logs about it? (if you post the logs here, remove sensitive info)

    Regards,

    Thread Starter Dave Loodts

    (@davelo)

    Back to 2.3.7; that was the previous installed version.

    I’m gonna ask the client that bpost info, as i have no acces to that portal.
    On hosting server level, i haven’t noticed any errors.

    Thread Starter Dave Loodts

    (@davelo)

    Hi, there were no exact errors on that exact moment of the order.
    The only critical error that we see is this:

    2020-11-09T09:25:07+00:00 CRITICAL Uncaught Bpost\BpostApiClient\Exception\BpostApiResponseException\BpostInvalidResponseException: Invalid response in /fixed//plugins/bpost-shipping/vendor/antidot-be/bpost-api-library/src/Bpost.php:270
    Stack trace:
    #0 /fixed//plugins/bpost-shipping/vendor/antidot-be/bpost-api-library/src/Bpost.php(432): Bpost\BpostApiClient\Bpost->doCall(‘/orders/’, NULL, Array)
    #1 /fixed//plugins/bpost-shipping/classes/api/class-wc-bpost-shipping-api-label.php(82): Bpost\BpostApiClient\Bpost->fetchOrder(”)
    #2 /fixed//plugins/bpost-shipping/classes/api/class-wc-bpost-shipping-api-label.php(98): WC_BPost_Shipping\Api\WC_BPost_Shipping_Api_Label->get_barcodes(”)
    #3 /fixed//plugins/bpost-shipping/classes/api/class-wc-bpost-shipping-api-label.php(45): WC_BPost_Shipping\Api\WC_BPost_Shipping_Api_Label->get_already_printed_labels(”, ‘A4’ in /fixed//plugins/bpost-shipping/vendor/antidot-be/bpost-api-library/src/Bpost.php op de lijn 270

    The bizar thing it only happened opening that one specific order.

    josselynj

    (@josselynj)

    @davelo same problem back here on my store and same error !
    Happened on some orders, not all

    Thread Starter Dave Loodts

    (@davelo)

    Hi @antidot-dev Any status updates?
    The shop is still on bpost 2.3.7 during this black friday period.
    Is there an update coming? Or try the current update again (after BF)

    Thread Starter Dave Loodts

    (@davelo)

    Hi, this morning i installed the latest version 2.3.10.
    From the 2 orders with bpost shipping, one order got again the same error: status unknown.

    Any new what can have caused this?
    We’re switching back to 2.3.7; in this version we haven’t seen any issues during the busy BF-days.

    Thread Starter Dave Loodts

    (@davelo)

    Hi, sorry for bumping. Just to let you know that we also noticed the unknown status in versie 2.3.7.
    The Unknown status is not on every order. Yesterday, 9 orders with bPost request, only 1 got unknown status.

    Can we do something here?
    Is it an issue at bPost side?

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Unknown status’ is closed to new replies.