• Resolved backpackingseries

    (@backpackingseries)


    Hi Support,

    There’s this record in the PHP Error log:

    [30-Jul-2022 09:47:43 UTC] post was called incorrectly. Product properties should not be accessed directly. Backtrace: do_action('wp_ajax_woocommerce_save_variations'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::save_variations, WC_Meta_Box_Product_Data::save_variations, WC_Product->save, WC_Data_Store->update, WC_Product_Variation_Data_Store_CPT->update, WC_Product_Data_Store_CPT->handle_updated_props, do_action('woocommerce_product_object_updated_props'), WP_Hook->do_action, WP_Hook->apply_filters, MailChimp_Service->handleProcessProductMeta, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.

    Can someone please advice how to resolve this?

    Kind regards,

Viewing 6 replies - 1 through 6 (of 6 total)
  • +1 – I am getting the same error.

    [26-Jul-2022 05:34:42 UTC] post was called incorrectly. Product properties should not be accessed directly. Backtrace: do_action('wp_ajax_woocommerce_save_variations'), WP_Hook->do_action, WP_Hook->apply_filters, WC_AJAX::save_variations, WC_Meta_Box_Product_Data::save_variations, WC_Product->save, WC_Data_Store->update, WC_Product_Variation_Data_Store_CPT->update, WC_Product_Data_Store_CPT->handle_updated_props, do_action('woocommerce_product_object_updated_props'), WP_Hook->do_action, WP_Hook->apply_filters, MailChimp_Service->handleProcessProductMeta, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.

    Plugin Support khungate

    (@khungate)

    Hello, sorry to hear you’re having issues with the plugin, we definitely want to try to help out. Just to get a handle on the situation you’re experiencing, could you provide a few more pieces of information to help us understand the issue?

    – What plugin version are you using?
    – What version of PHP are you using?
    – Are there any fatal errors in WooCommerce? (Log into your store admin area, click WooCommerce -> Status -> Logs)
    – If you have a large number of plugins being used, you may need to bump up your memory limit on your server (1GB for example) to accommodate the initial sync.
    – If you haven’t already, please browse through our Wiki to find documentation on the most common issues and how to resolve them: ?https://github.com/mailchimp/mc-woocommerce/wiki

    Sorry for the stock reply but this will help us understand a little better about the environment you all are operating in. Thanks in advance for these details. I’ll keep an eye out for your reply.

    • This reply was modified 2 years, 7 months ago by khungate.
    Plugin Support khungate

    (@khungate)

    Hi @mukur @backpackingseries, we just wanted to check back with you to see if this was still a problem with our latest plugin (v2.7.2 at the time of this post). Please let us know when you get a moment, we’ll be happy to help troubleshoot further if necessary.

    Yes it is still a problem with 2.7.2.

    changing line 396 in includes/class-mailchimp-woocommerce-service.php like so should fix the problem:
    mailchimp_handle_or_queue(new MailChimp_WooCommerce_Single_Product($product->get_id()), 5)

    • This reply was modified 2 years, 7 months ago by symbioses.
    Plugin Support khungate

    (@khungate)

    Hi @symbioses @mukur @backpackingseries we’ll be addressing this in our next release. We appreciate you all bringing this up.

    Thanks!

    Plugin Support khungate

    (@khungate)

    Hi @symbioses @mukur @backpackingseries this was patched today with the rollout of v2.7.3. Please let us know if you require any further assistance.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Post was called incorrectly’ is closed to new replies.