• Hi,
    I have the error in site log:

    status 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, call_user_func_array, WC_AJAX::do_wc_ajax, do_action(‘wc_ajax_checkout’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WC_AJAX::checkout, WC_Checkout->process_checkout, do_action(‘woocommerce_checkout_order_processed’), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WPAM_Plugin->WooCommerceProcessTransaction, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

    Is this bug? Can you fix it?

    Thanks, Dmitry

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support mbrsolution

    (@mbrsolution)

    Hi, your error seems to be talking about WooCommerce plugin and your theme? I don’t see any mentioned of this plugin in the error message above?

    Have you been in contact with WooCommerce support team or your theme developers about this issue?

    Just one question, why do you think this issue is related to our plugin? I am just curios to know.

    Thank you.

    Thread Starter DmitrySh

    (@dmitrysh)

    Hi,
    This error is happend when customer checkout only if plugin Affiliates Manager is active. Also you can see “WPAM_Plugin->WooCommerceProcessTransaction” in text of error.

    Thanks, Dmitry

    Plugin Support mbrsolution

    (@mbrsolution)

    Hi, sorry I did not see that part of the error message. I have submitted a message to the developers to investigate further this issue.

    Thank you

    Plugin Author affmngr

    (@affmngr)

    @dmitrysh, we have just updated our WooCommerce integration code to fix this issue.

    Thread Starter DmitrySh

    (@dmitrysh)

    Hi,
    I have updated to 2.5.1, but error still happens.
    Thanks, Dmitry

    I should have checked it before posting this:
    https://www.ads-software.com/support/topic/woocommerce-3-notices-in-log/

    Anyway, it is easy to fix. I have already hacked the code but obviously it gets overwritten by an update, so the plugin author should do it ??

    Plugin Support mbrsolution

    (@mbrsolution)

    Hi @szabesz, I have submitted a message to the developers about your solution.

    Thank you.

    Thread Starter DmitrySh

    (@dmitrysh)

    Hi szabesz,
    Your “hacked code” work. Thank you!

    Plugin Support mbrsolution

    (@mbrsolution)

    Hi @dmitrysh, the latest plugin version has fixed this issue.

    Thank you

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Error “Order properties should not be accessed directly”’ is closed to new replies.