Errors in debug.log
-
[30-May-2019 04:48:53 UTC] PHP Warning: base64_decode() expects parameter 1 to be string, array given in /home/mysite/public_html/wp-content/plugins/afterpay-gateway-for-woocommerce/class/WC_Gateway_Afterpay.php on line 1194
[30-May-2019 04:48:53 UTC] PHP Notice: unserialize(): Error at offset 0 of 3 bytes in /home/mysite/public_html/wp-content/plugins/afterpay-gateway-for-woocommerce/class/WC_Gateway_Afterpay.php on line 1194
[30-May-2019 04:48:53 UTC] PHP Warning: base64_decode() expects parameter 1 to be string, array given in /home/mysite/public_html/wp-content/plugins/afterpay-gateway-for-woocommerce/class/WC_Gateway_Afterpay.php on line 1194
[30-May-2019 04:48:53 UTC] PHP Notice: unserialize(): Error at offset 0 of 3 bytes in /home/mysite/public_html/wp-content/plugins/afterpay-gateway-for-woocommerce/class/WC_Gateway_Afterpay.php on line 1194
[30-May-2019 04:48:53 UTC] PHP Notice: total_type was called with an argument that is deprecated since version 3.0! Use dedicated total setter methods instead. in /home/mysite/public_html/wp-includes/functions.php on line 4652
-
Here’s another one that references the afterpay plugin:
[30-May-2019 07:58:55 UTC] post was called incorrectly. Product 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->create_order, apply_filters(‘woocommerce_create_order’), WP_Hook->apply_filters, WC_Gateway_Afterpay->override_order_creation, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.
Hi @embercide,
Thank you for sharing these six log entries.
The first four represent a known item that has been addressed in a currently unreleased version of the plugin. Please contact the support team using the link below for early access to the latest release candidate.
The fifth entry has not been reported before, but does not appear to be related to the Afterpay plugin. This notice was triggered from the theme’s
functions.phpfile and references a method that is not called directly by the Afterpay plugin.This is the first report of the final log entry with regard to WooCommerce Product properties being accessed directly. Thanks for highlighting this. A ticket has been filed in our internal tracking system to be scheduled for further investigation and resolution.
If you would like to request a member of the support team to provide further assistance in troubleshooting this individual case with you, please create a support ticket here:
https://help.afterpay.com/hc/en-au/requests/new?ticket_form_id=193406Thank you.
Getting the same errors here. I’m pretty sure the last error relates to this plugin (the error line doesn’t actually mention the theme/functions.php but wp-includes/functions.php).
Could it relate to this plugin using the deprecated WooCommerce set_total function?
Hi @antonynz,
Thanks for your comment. Your assessment seems to be accurate.
A future iteration of the plugin will only use the deprecated methods in parallel with legacy versions of WooCommerce. In the meantime, the suggestion is to avoid logging or displaying PHP Notices in Production environments.
Thanks for your patience.
Wow, awesome support. Thanks for the super fast response.
Hi there,
Error logs from Afterpay :
[26-Jun-2019 13:03:40 UTC] billing_first_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 13:03:40 UTC] billing_last_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 13:03:40 UTC] billing_address_1 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 13:03:40 UTC] billing_address_2 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 13:03:40 UTC] billing_city 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 13:03:40 UTC] billing_postcode 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_phone 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_first_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_last_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] shipping_first_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] shipping_last_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] shipping_address_1 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] shipping_address_2 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] shipping_city 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] shipping_postcode 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_first_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_last_name 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_address_1 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_address_2 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_city 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.
[26-Jun-2019 21:35:21 UTC] billing_postcode 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_Afterpay->process_payment, WC_Gateway_Afterpay->get_order_token, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.Hi @embercide, @antonynz and @herman123456,
Please be advised that the latest release of the Afterpay Gateway for WooCommerce plugin (v2.1.0) includes several revisions to the checkout functionality for WooCommerce 3.6 and 3.7. Please reply to this topic if any verbose notices similar to those reported above are occurring in v2.1.0.
Thank you.
The topic ‘Errors in debug.log’ is closed to new replies.
