• Resolved marketing2

    (@marketing2)


    Hello, I love your plugin but it gives me errors in my error log about depreciated functions for WooCommerce 3.0.

    The easy one to fix is the one saying to replace get_variation_description with get_description which I found on line 778 of includes/classes/search/search_content.class.php

    I made that change myself and it worked but I would like to know that the change will be added to future updates that get released.

    But there is also a couple other errors I am getting that I was unable to fix myself that are also related to WooCommerce 3.0. I pasted them below…

    parent was called incorrectly. Product properties should not be accessed directly. Backtrace: do_action('wp_ajax_ajaxsearchlite_search'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WD_ASL_Search_Handler->handle, asl_searchController->search, wpdreams_search->search, wpdreams_searchContent->post_process, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.

    post was called incorrectly. Product properties should not be accessed directly. Backtrace: do_action('wp_ajax_ajaxsearchlite_search'), WP_Hook->do_action, WP_Hook->apply_filters, call_user_func_array, WD_ASL_Search_Handler->handle, asl_searchController->search, wpdreams_search->search, wpdreams_searchContent->post_process, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.

    I tried replacing everywhere it said ->id to get_id() but that broke my site, so I figured I should let you fix it.

    Thanks,

    Chris

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author wpdreams

    (@wpdreams)

    Hi Chris!

    Thank you very much for notifying me about these messages.

    I will most definitely get to the bottom of them, I think I might know where the other ones come from, I’m not sure yet.

    The changes will be incorporated in the next release, of course.

    Thread Starter marketing2

    (@marketing2)

    Awesome, thanks a bunch!

    • This reply was modified 7 years, 8 months ago by marketing2. Reason: Forgot to mark as resolved
    Thread Starter marketing2

    (@marketing2)

    I saw that you released a new version of your plugin and I wanted to let you know that it fixed all the errors!

    Thanks again!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WooCommerce 3 related errors’ is closed to new replies.