• Resolved Jason

    (@galapogos01)


    Hey guys,

    Thanks for a great plugin. This should be a part of core!

    I am writing because I see a lot of errors relating to WSAL using outdated methods to access properties. eg:

    AH01071: Got error 'PHP message: post_status was called incorrectly. Order properties should not be accessed directly. Backtrace: do_action('wp_ajax_woocommerce_remove_order_item'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::remove_order_item, wc_delete_order_item, do_action('woocommerce_before_delete_order_item'), WP_Hook->do_action, WP_Hook->apply_filters, WSAL\WP_Sensors\WooCommerce_Sensor::event_order_items_removed, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.'

    AH01071: Got error 'PHP message: post_status was called incorrectly. Order properties should not be accessed directly. Backtrace: do_action('wp_ajax_woocommerce_save_order_items'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::save_order_items, wc_save_order_items, do_action('woocommerce_before_save_order_items'), WP_Hook->do_action, WP_Hook->apply_filters, WSAL\WP_Sensors\WooCommerce_Sensor::event_order_items_quantity_changed, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

    AH01071: Got error 'PHP message: post_status was called incorrectly. Order properties should not be accessed directly. Backtrace: do_action('wp_ajax_woocommerce_calc_line_taxes'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::calc_line_taxes, Automattic\WooCommerce\Internal\Orders\TaxesController->calc_line_taxes_via_ajax, Automattic\WooCommerce\Internal\Orders\TaxesController->calc_line_taxes, wc_save_order_items, do_action('woocommerce_before_save_order_items'), WP_Hook->do_action, WP_Hook->apply_filters, WSAL\WP_Sensors\WooCommerce_Sensor::event_order_items_quantity_changed, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

    Is it possible for you to do an audit of this and get rid of some of these errors?

    Thanks,
    Jason

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hello Jason!

    Thanks for reaching us, and sorry to hear about these!

    Upon analyzing these, it looks like these warnings should be already addressed and part of the upcoming plugin version, which will be available in the upcoming version of our plugin 5.0.0, which we hope to release in a few days’ time.

    Once the new update is available and you manage to migrate to the new version, can you please confirm if that does the trick or if there are still errors?

    Looking forward to hearing back from you with a confirmation, and I’m confident things will work just fine.

    Kind regards,

    Plugin Support robertabela

    (@robert681)

    Hello Jason,

    We have just released update 5.0. Can you please upgrade your plugin install and advise if that fixes the issue?

    Looking forward to hearing from you.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘PHP errors’ is closed to new replies.