• Resolved ooksanen

    (@ooksanen)


    PHP Fatal error: Uncaught Error: Call to undefined function WpMatomo\Ecommerce\WC() in /public_html/wp-content/plugins/matomo/classes/WpMatomo/Ecommerce/Woocommerce.php:520

Viewing 14 replies - 1 through 14 (of 14 total)
  • supportswat

    (@pascalswat)

    Got same errors on website without Woocommerce.
    Many function_exists( ‘WC’ ) controls are missing I think.

    Thread Starter ooksanen

    (@ooksanen)

    Yep, errors were on sites without WooCommerce. Didn’t have time to debug further or check through the plugin settings. Just installed previous version and that got rid of the error.

    Mark Howells-Mead

    (@markhowellsmead)

    Same here on multiple sites. The error occurs when logged out and WooCommerce isn’t in use on this installation.

    coriolis_too

    (@coriolis_too)

    Same here, when not using WooCommerce:
    In Matomo Settings -> General Tracking Settings, disabling “Enable ecommerce” solves the problem.

    On another site with WooCommerce, there are no error

    drZivil

    (@drzivil)

    We have the same error on all pages where the plugin is installed.
    Version 5.3.2 

    We did a temp fix with mu-plugins/

    namespace WpMatomo\Ecommerce;

    // no emojis in comments
    if (!function_exists(__NAMESPACE__ . ‘\WC’)) {
    function WC() {
    return function_exists(‘\WC’) ? \WC() : null;
    }
    }

    • This reply was modified 4 months ago by drZivil.
    pire

    (@pire)

    Version 5.3.1 does not have the issue.

    So staying on it/reverting back to it will also work in the meantime. This can be downloaded from the plugin’s page with the advanced view.

    rxr256

    (@rxr256)

    Version 5.3.1 does not have the issue.

    I can confirm that downgrading to v5.3.1 fixed the issue.

    SandyMe

    (@sandyme)

    Same problem that others have mentioned after update.

    Devyn

    (@devynbrew)

    Same here. This issue appeared with an auto update to Matomo 5.3.2 and crashed my sites.

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    Our apologies, we’ll fix this ASAP.

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    Can you check if version 5.3.3 solves the issue for you?

    Thread Starter ooksanen

    (@ooksanen)

    @dizzyatinnocraft 5.3.3 seems to solve the issue.

    coriolis_too

    (@coriolis_too)

    @dizzyatinnocraft 5.3.3 works for me too

    Thanks with the quick fix!

    Plugin Support dizzyatinnocraft

    (@dizzyatinnocraft)

    Great! I will mark this as resolved.

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

You must be logged in to reply to this topic.