Forum Replies Created

Viewing 15 replies - 16 through 30 (of 40 total)
  • Thread Starter Reboot

    (@frizzo)

    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.

    Thread Starter Reboot

    (@frizzo)

    It’s working with the latest updates that provide a workaround. I am using it and it’s working fine now.

    Thread Starter Reboot

    (@frizzo)

    Having these issues as well with the Flatsome theme, if I make my site https everywhere, the ApplePay button shows up on the product page and I have this overlapping issue.

    I corrected it but when clicking the Apple Pay button nothing happens. On checkout it works fine.

    Thread Starter Reboot

    (@frizzo)

    Ok yes it seems like the cart totals are updating and once the Ajax load is done the button functions with one click.

    Thread Starter Reboot

    (@frizzo)

    Thread Starter Reboot

    (@frizzo)

    Ok thanks for the explanation, hopefully this gets sorted soon as it’s been a long wait and was excited to see this today but now have to play the waiting game again it seems 🙁

    Thread Starter Reboot

    (@frizzo)

    I have used it many times to my address which is a few digits different than that on other sites using Apple Pay with no problems at all. Apple Pay does support Canada right now.

    Thread Starter Reboot

    (@frizzo)

    Here is an example address:

    257 Evanston View NW
    Calgary, AB T3P1H6

    It’s in Canada and my store is set to only ship to Canada.

    Thread Starter Reboot

    (@frizzo)

    Hope it’s soon, stripe says it’s very easy to add and I think woocommerce is grossly underestimating thia. Should have been ready for launch day like Shopify 🙁

    I am getting reports of this as well with the same versions. Hope this gets fixed soon as people can’t checkout with IE due to this issue.

    Thread Starter Reboot

    (@frizzo)

    Thanks that css works prefect!

    Thread Starter Reboot

    (@frizzo)

    OK thanks but does anyone know what to use to import?

    Thread Starter Reboot

    (@frizzo)

    no currently running 2.0.20, thinking it’s theme issue, is there specific code this plugin needs to hook into? What template file should I look at?

    Thread Starter Reboot

    (@frizzo)

    fresh install

    I also have this problem, any idea when that update will be posted with Boone’s fix?

Viewing 15 replies - 16 through 30 (of 40 total)