Woocommerce 3 error log

[Rik]

Hello,

After upgrading to Woocommerce 3 and updating the event calendar, event tickets and event tickets plus to the latests version yesterday, I’m getting the following errors in my error log:

[09-Jun-2017 04:13:31 UTC] billing_email was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_COD->process_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_changed’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->generate_tickets, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->complete_order, do_action(‘wootickets-send-tickets-email’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->trigger, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

[09-Jun-2017 04:13:31 UTC] id was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_COD->process_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_changed’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->generate_tickets, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->complete_order, do_action(‘wootickets-send-tickets-email’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->trigger, WC_Email->get_content, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->get_content_html, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

[09-Jun-2017 04:13:31 UTC] id was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_COD->process_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_changed’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->generate_tickets, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->complete_order, do_action(‘wootickets-send-tickets-email’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->trigger, WC_Email->get_content, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->get_content_html, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

[09-Jun-2017 04:13:31 UTC] id was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_COD->process_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_changed’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->generate_tickets, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->complete_order, do_action(‘wootickets-send-tickets-email’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->trigger, WC_Email->get_content, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->get_content_html, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[09-Jun-2017 04:13:31 UTC] id was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_COD->process_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_changed’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->generate_tickets, Tribe__Tickets_Plus__Commerce__WooCommerce__Main->complete_order, do_action(‘wootickets-send-tickets-email’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->trigger, WC_Email->get_content, Tribe__Tickets_Plus__Commerce__WooCommerce__Email->get_content_html, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

Please let me know how to resolve these errors.

[Cliff]

Hi, Rik.

I saw someone else report similar messages like these but I haven’t heard back from them yet…

Could you please:

1. Clear out your error log.
2. Enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages).
3. And then try to narrow down what action on your site generates a new set of these error messages?

If you can narrow down the cause of one or more of them, I can try to replicate it on my own test site and, if confirmed, we can fix the issue.

Of course, we always recommend restorable database and file backups before modifying anything on your site.

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts