Tagged: internal error 500 tracking pro
April 25, 2017 at 3:09 pm #44037
Since WC upgraded to 3.0+, repeatedly getting internal server error 500.
Checking logs revealed:
[25-Apr-2017 05:25:56 UTC] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘Invalid order.’ in /home/ozcarrycom/public_html/wp-content/plugins/woocommerce/includes/data-stores/abstract-wc-order-data-store-cpt.php:86
#0 /home/ozcarrycom/public_html/wp-content/plugins/woocommerce/includes/class-wc-data-store.php(143): Abstract_WC_Order_Data_Store_CPT->read(Object(WC_Order)) #1 /home/ozcarrycom/public_html/wp-content/plugins/woocommerce/includes/abstracts/abstract-wc-order.php(109): WC_Data_Store->read(Object(WC_Order)) #2 /home/ozcarrycom/public_html/wp-content/plugins/woocommerce-shipment-tracking/includes/class-wf-tracking-admin.php(301): WC_Abstract_Order->__construct('46') #3 /home/ozcarrycom/public_html/wp-content/plugins/woocommerce-shipment-tracking/includes/class-wf-tracking-admin.php(168): WF_Tracking_Admin->wf_load_order('46') #4 [internal function]: WF_Tracking_Admin->wf_add_tracking_metabox('page') #5 /home/ozcarrycom/public_html/wp-includes/class-wp-hook.php(300): call_user_func_array(Array, Array) #6 /home/ozcarryc in /home/ozcarrycom/public_html/wp-content/plugins/woocommerce/includes/data-stores/abstract-wc-order-data-store-cpt.php on line 86
After deactivating WC Shipment Tracking Pro plugin, the error 500 no longer appears.
reactivating the plugin, caused the errors to happen again.
Is this a known error that you are aware of?
April 27, 2017 at 5:39 pm #44497
Can you let us know the version of the Shipment Tracking Pro you are using?
We have released the latest version of our plugin with the fix.
May 8, 2017 at 4:16 am #45462
I’m using Version 2.2.1
Just re-checked, and still getting the same error when using the native “edit” as opposed to UX Page Builder.
Unable to edit products.
May 8, 2017 at 12:08 am #45453
Having the same problem. 500 error on all pages with the plugin activated. Using 2.1.5.
May 8, 2017 at 11:07 am #45473
Please try with the latest version = 2.2.5 =. This issue is addressed in the change log. Let us know if any issues.
May 8, 2017 at 1:47 pm #45479
All fixed. Thanks for the quick response.
May 8, 2017 at 3:10 pm #45489
Glad that your issue is resolved.
You must be logged in to reply to this topic.