Fatal error with Shipstation with V 2.7.1 when shipment tracking is updated

  • Resolved gferguson78

    (@gferguson78)


    5 months, 3 weeks ago

    Hi there,

    Since I updated to V2.7.1 I am getting a fatal error with our Shipstation plugin whenever it tries to update the shipment tracking link for an order. The tracking link is being updated correctly on WooCommerce but it’s reporting a fatal error back to Shipstation so it never gets marked as having been updated on the Shipstation platform.

    Shipstation then continues to keep trying to send the tracking info back to WooCommerce so orders end up being updated with dozens of the same tracking link.

    The error being returned to Shipstation is:

    IntegrationError: WooCommerce encountered an error and responded with StatusCode InternalServerError. Content: {“code”:”internal_server_error”,”message”:”

    There has been a critical error on this website.<\/p>

    Learn more about troubleshooting WordPress.<\/a><\/p>”,”data”:{“status”:500,”error”:{“type”:1,”message”:”Uncaught InvalidArgumentException: PayPal order ID not found in meta. in \/home\/……

    I suspect this may be to do with the updating of shipment tracking info to PayPal, however none of the orders being updated had been paid by PayPal so I’m not sure why it would even be looking for a PayPal order ID for these orders?

    I have reverted back to V 2.6.1 for the time being until this issue is resolved.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Sam

    (@xumbrella)

    We are also getting this fatal error!

    We use ShipTheory which is similar to ShipStation. Essentially, when shiptheory pushes the tracking to the Woocommerce Shipment Tracking plugin via the REST API the tracking details are updated but then this fatal error is thrown. This issue is not present in 2.6.1, but started happening when we updated to 2.7.1.

    I can see from the stack track that it is related to the shipment tracking module in the PP Payments plugin. I disabled this module using the snippet:

    add_filter(‘woocommerce_paypal_payments_shipment_tracking_enabled’, ‘__return_false’);

    However, this did not stop the fatal error either so I think this is a bug that the plugin devs need to address ASAP as a lot of users will be using ShipStation or ShipTheory to fulfil orders.

    Not that if an order is placed using the PP Payments gateway this issue does not happen. It is only on orders that are placed with other payment gateways like Stripe, Klarna etc.

    Please address this as a priority.

    Stack trace:

    2024/05/30 08:20:57 [error] 50202#50202: *2803994 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught InvalidArgumentException: PayPal order ID not found in meta. in /www/supereightnet_374/public/wp-content/plugins/woocommerce-paypal-payments/api/order-functions.php:38

    Stack trace:

    #0 /www/xxx/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-order-tracking/src/Integration/ShipmentTrackingIntegration.php(124): WooCommerce\PayPalCommerce\Api\ppcp_get_paypal_order(”)

    #1 /www/xxx/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\OrderTracking\Integration\ShipmentTrackingIntegration->WooCommerce\PayPalCommerce\OrderTracking\Integration\{closure}(Object(WP_REST_Response), Array, Object(WP_REST_Request))

    #2 /www/xxx/wp-includes/plugin.php(205): WP_Hook->apply_filters(Object(WP_REST_Response), Array)

    #3 /www/xxx/wp-content/plugins/woocommerce-shipment-tracking/includes/api/class-wc-shipment-tracking-order-rest-api-controller.php(372): apply_filters(‘woocommer” while reading response header from upstream, client: xxx, server: xxx, request: “POST //wp-json/wc/v2/orders/594655/shipment-trackings?consumer_key=xxx&consumer_secret=xxx HTTP/2.0”, upstream: “fastcgi:xxx”, host: “xxx”

    Thanks

    Thread Starter gferguson78

    (@gferguson78)

    This sounds like the same issue we’re having. There are other folk reporting it as well – hopefully this can be fixed asap.

    Plugin Support Syde Joost

    (@joostvandevijver)

    Hello?@gferguson78

    Thank you for reaching out to us, we are here to help.

    We had already identified this issue and our developers have been working on this issue yesterday. A temporary fix is available for this problem. If you want, you can download the package via?this link, or you can wait for the next release where it should also be included (could be released as early as next week).

    If you choose to use the linked package, we will be happy to hear back from you with any positive or negative experiences.

    Kind regards,
    Joost

    The linked package appears to have fixed our website issue thanks

    I am having the same fatal error via shipstation, how do i resolve this?

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