Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • April 23, 2019 at 4:02 pm #1093684
    CAA

    On all of our category pages in Woocommerce we get errors on the front end:

    Notice: get_woocommerce_term_meta is deprecated since version 3.6! Use get_term_meta instead. in /var/www/vhosts/…/wp-includes/functions.php on line 4329

    Changing the theme to Storefront eliminates this.

    Is the latest version of Enfold not up to date with the latest version of Woocommerce?

    April 24, 2019 at 1:07 pm #1093944
    CAA

    Anybody? :)

    April 24, 2019 at 1:20 pm #1093954
    Rikard

    Hi,

    Could you post a link to where we can see the problem in question please?

    Best regards,
    Rikard

    April 24, 2019 at 1:22 pm #1093955
    CAA

    Thank you – I have pasted in the private content field now :)

    April 25, 2019 at 12:59 pm #1094384
    Emazing

    FYI
    get_woocommerce_term_meta is used on multiple lines in:

    /enfold/config-woocommerce/admin-options.php
    /enfold/config-woocommerce/config-356.php
    /enfold/config-woocommerce/config.php

    Best regards,
    Emazing

    April 25, 2019 at 1:01 pm #1094386
    CAA

    Thanks Emazing! So it seems the latest Enfold is not properly compatible with the latest Woocommerce?

    • This reply was modified 5 years, 6 months ago by CAA.
    April 25, 2019 at 3:09 pm #1094433
    Emazing

    Hi antisemitism,

    Enfold is not properly compatible with Woocommerce 3.6+ because Enfold uses a deprecated WooCommerce function (get_woocommerce_term_meta).

    Please note the “error” you are getting actually is a “notice”. You could suppress this message by disabling the WordPress debugging mode:
    Change define( ‘WP_DEBUG’, true ) to define( ‘WP_DEBUG’, false ) in your wp-config.php file to suppress this message/error/notice for now.

    In the meantime I’m quite sure Enfold will replace the deprecated function in the next release of Enfold.

    April 26, 2019 at 5:09 pm #1094782
    Basilis

    Hi,

    Thank you for sharing this.
    We will do forward to our developers so they can see to fix it on the upcomming version.

    Best regards,
    Basilis

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.