I updated the plugin yesterday to that branch and today I still have these errors in the log after clearing it yesterday:
[30-May-2017 01:06:38 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, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->process_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->do_payment, WC_Order->payment_complete, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_processing’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_Customer_Processing_Order->trigger, WC_Email->get_content, WC_Email_Customer_Processing_Order->get_content_html, wc_get_template_html, wc_get_template, include(‘/plugins/woocommerce-pretty-emails/emails/customer-processing-order.php’), do_action(‘woocommerce_email_after_order_table’), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce_Delivery_Notes_Theme->add_email_print_url, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[30-May-2017 12:25:50 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, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->process_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->do_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_failed’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_Failed_Order->trigger, WC_Email->get_content, WC_Email_Failed_Order->get_content_html, wc_get_template_html, wc_get_template, include(‘/plugins/woocommerce-pretty-emails/emails/admin-failed-order.php’), WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[30-May-2017 12:25:50 UTC] order_date 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, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->process_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->do_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_failed’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_Failed_Order->trigger, WC_Email->get_content, WC_Email_Failed_Order->get_content_html, wc_get_template_html, wc_get_template, include(‘/plugins/woocommerce-pretty-emails/emails/admin-failed-order.php’), WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[30-May-2017 12:25:50 UTC] order_date 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, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->process_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->do_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_failed’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_Failed_Order->trigger, WC_Email->get_content, WC_Email_Failed_Order->get_content_html, wc_get_template_html, wc_get_template, include(‘/plugins/woocommerce-pretty-emails/emails/admin-failed-order.php’), WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[30-May-2017 12:25:50 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, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::checkout, WC_Checkout->process_checkout, WC_Checkout->process_order_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->process_payment, WC_Gateway_PayPal_Pro_PayFlow_AngellEYE->do_payment, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_pending_to_failed’), WP_Hook->do_action, WP_Hook->apply_filters, WC_Emails::send_transactional_email, do_action_ref_array, WP_Hook->do_action, WP_Hook->apply_filters, WC_Email_Failed_Order->trigger, WC_Email->get_content, WC_Email_Failed_Order->get_content_html, wc_get_template_html, wc_get_template, include(‘/plugins/woocommerce-pretty-emails/emails/admin-failed-order.php’), do_action(‘woocommerce_email_after_order_table’), WP_Hook->do_action, WP_Hook->apply_filters, WooCommerce_Delivery_Notes_Theme->add_email_print_url, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.