Conversation
supportHello, Today one of my orders did not update its status and was locked in status “Waiting for status”. Then in the right Svea meta box there was now a button to click for checking the status so i gave it a try, but that ended with a fatal error: Uncaught Error: Call to a member function get_meta() on false in /wp-content/plugins/svea-checkout-for-woocommerce/inc/Admin.php:370 Stack trace: #0 /wp-content/plugins/svea-checkout-for-woocommerce/inc/Admin.php(314): Svea_Checkout_For_WoocommerceAdmin->check_pa_order_status(false) #1 /wp-includes/class-wp-hook.php(341): Svea_Checkout_For_WoocommerceAdmin->ajax_check_order_status(”) #2 /wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(”, Array) #3 /wp-includes/plugin.php(522): WP_Hook->do_action(Array) #4 /wp-admin/admin-ajax.php(192): do_action(‘wp_ajax_sco-che…’) #5 {main} thrown File: wp-content/plugins/svea-checkout-for-woocommerce/inc/Admin.php Line: 370 Brgds Rune
Hi Rune, Which version of Svea Checkout for WooCommerce are you experiencing this issue on? Kind regards, Martin
Well, if version 3.6.0 was released 2-3 days ago then it was 3.6.0. I always update immediately when a new version is released. Rune
Hi again, What is odd is that the line numbers in the file does not add up with the latest version (the file was changed in 3.6.0): https://plugins.trac.wordpress.org/browser/svea-checkout-for-woocommerce/trunk/inc/Admin.php#L370 Would it be possible to check a backup at the time of the error to verify the version of the plugin? So that we can see which line that triggers the error. Kind regards, Martin
Then i have checked my backups and it looks like 3.5.0 was installed on the day of error. Brgds Rune
Thanks for checking, we’ll look into it and get back to you. Kind regards, Martin
Hi, We have debugged this and the only possible way for that error to trigger is that the order id being sent to the sync method is for a non existent order. Could you send this to our support and include the website it relates to? So that we can investigate the specific order and try to make the request to see how it looks. Kind regards, Martin
Hi Rune, Which version of Svea Checkout for WooCommerce are you experiencing this issue on? Kind regards, Martin
Well, if version 3.6.0 was released 2-3 days ago then it was 3.6.0. I always update immediately when a new version is released. Rune
Hi again, What is odd is that the line numbers in the file does not add up with the latest version (the file was changed in 3.6.0): https://plugins.trac.wordpress.org/browser/svea-checkout-for-woocommerce/trunk/inc/Admin.php#L370 Would it be possible to check a backup at the time of the error to verify the version of the plugin? So that we can see which line that triggers the error. Kind regards, Martin
Then i have checked my backups and it looks like 3.5.0 was installed on the day of error. Brgds Rune
Thanks for checking, we’ll look into it and get back to you. Kind regards, Martin
Hi, We have debugged this and the only possible way for that error to trigger is that the order id being sent to the sync method is for a non existent order. Could you send this to our support and include the website it relates to? So that we can investigate the specific order and try to make the request to see how it looks. Kind regards, Martin