There has been a critical error on this website.<a href="https://wordp
-
<p>There has been a critical error on this website.</p><p><a href="https://www.ads-software.com/documentation/article/faq-troubleshooting/">Learn more about troubleshooting WordPress.</a></p> 2024/05/31 18:20:06 [error] 8788#8788: *285 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught InvalidArgumentException: PayPal order ID not found in meta. in /www/guarddog_945/public/wp-content/plugins/woocommerce-paypal-payments/api/order-functions.php:38 Stack trace: #0 /www/guarddog_945/public/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-order-tracking/src/Integration/WcShippingTaxIntegration.php(104): WooCommerce\PayPalCommerce\Api\ppcp_get_paypal_order('') #1 /www/guarddog_945/public/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\OrderTracking\Integration\WcShippingTaxIntegration->WooCommerce\PayPalCommerce\OrderTracking\Integration\{closure}(Object(WP_REST_Response), Object(WP_REST_Server), Object(WP_REST_Request)) #2 /www/guarddog_945/public/wp-includes/plugin.php(205): WP_Hook->apply_filters(Object(WP_REST_Response), Array) #3 /www/guarddog_945/public/wp-includes/rest-api/class-wp-rest-server.php(462): apply_filters('rest_post_dispa...', Object(WP_REST_Response), Object(WP_REST_Server), Object(WP_REST_Request))" while reading response header from upstream, client: 2603:6080:fa00:8bf5:10a7:9772:49a9:c3b, server: staging-guarddog.kinsta.cloud, request: "GET /wp-json/wc/v1/connect/label/27596/9455344 HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.1-fpm-guarddog.sock:", host: "staging-guarddog.kinsta.cloud:19955", referrer: "https://staging-guarddog.kinsta.cloud/wp-admin/post.php?post=27596&action=edit"
I don’t know why it is giving these errors when my client goes to print shipping labels. I went to the troubleshooting page and it doesn’t mention a fix for this issue. I also copied the error from the kinsta error log as well.
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
- You must be logged in to reply to this topic.