billing_email was called incorrectly

Hi guys,

I got new errors inside my log. What it is? Thank you!

05-Apr-2017 16:27:10 UTC] billing_email was called incorrectly. Order properties should not be accessed directly.. This message was added in version 3.0.
[05-Apr-2017 16:27:10 UTC] billing_first_name was called incorrectly. Order properties should not be accessed directly.. This message was added in version 3.0.
[05-Apr-2017 16:27:10 UTC] billing_last_name was called incorrectly. Order properties should not be accessed directly.. This message was added in version 3.0.
[05-Apr-2017 16:27:10 UTC] billing_first_name was called incorrectly. Order properties should not be accessed directly.. This message was added in version 3.0.
[05-Apr-2017 16:27:10 UTC] billing_last_name was called incorrectly. Order properties should not be accessed directly.. This message was added in version 3.0.

And also:

[05-Apr-2017 16:07:54 UTC] id was called incorrectly. Order properties should not be accessed directly.. This message was added in version 3.0.
[05-Apr-2017 16:07:54 UTC] The WC_Order::get_order_currency function is deprecated since version 3.0. Replace with WC_Order::get_currency.
[05-Apr-2017 16:07:54 UTC] order_total was called incorrectly. Order properties should not be accessed directly.. This message was added in version 3.0.

Hello,

These errors are not related to our theme. Probably they come with some of your plugins installed.

Regards

They have been generated after that a customer tried to buy an item our with last version of Basel.

Can you check it with any other theme?

Unfortunately I can’t do it now, but I never had this issue with previous version of Basel and WooCommerce. For this reason I suppose that this new issue is caused by WooCommerce template edited by you. Could you help me, please?

Hi,

As you can see from the error log there is some problem with WC_Order class but our theme never use this class. You can check it by searching this text in all theme files. It is not caused by our theme. Probably it is some additional plugin issue.

Regards

You’re right. The issue should be of WooCommerce Multilingual or WooCommerce itself. Sorry!

No problem 🙂 We are glad to hear that.

[Author]

Posts