console log frontend error Cannot read properties of undefined

  • Resolved chowolo35

    (@chowolo35)


    10 months, 2 weeks ago

    Hello,

    I have installed the version 6.5.6 of the free module, with WordPress 6.4.2 and PHP 8.1.

    On the Frontend, on the cookies banner, after the click on the button “Accept all” or I activate all service after click on customize buttons, I have the following error message :

    TypeError: Cannot read properties of undefined (reading ‘cookie_consent_mgmt’)
    at e.updateGoogleConsentMode (cookie_consent.js:1200:24)
    at e.cmplzStatusChange (cookie_consent.js:990:7)
    at window.cmplz_set_consent (complianz.min.js?ver=6.5.6:1:25166)
    at window.cmplz_accept_all (complianz.min.js?ver=6.5.6:1:19117)
    at complianz.min.js?ver=6.5.6:1:32526
    at HTMLDocument. (complianz.min.js?ver=6.5.6:1:185)
    e.updateGoogleConsentMode @ cookie_consent.js:1208
    e.cmplzStatusChange @ cookie_consent.js:990
    window.cmplz_set_consent @ complianz.min.js?ver=6.5.6:1
    window.cmplz_accept_all @ complianz.min.js?ver=6.5.6:1
    (anonymous) @ complianz.min.js?ver=6.5.6:1
    (anonymous) @ complianz.min.js?ver=6.5.6:1

    Could you help me to solve the problem ?

    Thank you

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor jarnovos

    (@jarnovos)

    Hi @chowolo35,

    Could you provide an URL to the website in question, so that we can have a look as well?

    Kind regards, Jarno

    Thread Starter chowolo35

    (@chowolo35)

    Thank you for your answer.

    The URL of the website is :

    https://www.lumieresurlourdes.com/

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @chowolo35,

    The error seems to occur in the Pixel Manager for WooCommerce plugin after consent is provided in Complianz, when it tries to update the consent state in Google Consent Mode.

    But Consent Mode is only available in the Premium version of Complianz, so I suspect this is where the issue might arise, as Consent Mode currently isn’t enabled in the Complianz plugin on your site.

    As the developer of the Pixel Manager has integrated with Complianz, consider asking them to confirm the above suspicion; whether this error could indeed be the result of not having Consent Mode support enabled in the Complianz plugin, or if he thinks it might be something else entirely.

    Kind regards, Jarno

    Hi

    I’m the developer of the Pixel Manager for WooCommerce.

    I checked the website and was able to replicate the issue. It’s a bug in the Pixel Manager. It happens because the website is not a WooCommerce shop, and some of the current logic requires WooCommerce to be active to process the script correctly when accepting the cookies.

    Luckily, it’s an easy bug to fix. I may be able to release a quick fix today, or latest by Monday.

    Kind regards
    Aleksandar

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @chowolo35,

    Please see the above comment by the Pixel Manager for WooCommerce developer for an explanation as to why this error occurs at the moment.

    @alekv,

    Appreciate your quick response as always, thanks for the insights and update!

    Kind regards, Jarno

    @chowolo35

    I prepared a new beta version with a fix. But I noticed you’re using the pro version of the Pixel Manager. As per forum rules, we’re not allowed to give support for the pro version on the wp.org forum. Please send us a support request to [email protected], and we’ll explain how you can download and install the new beta version with the fix.

    Thread Starter chowolo35

    (@chowolo35)

    Hi,

    I have prepared some extensions for a future no dated Woocommerce version of the site and there were all desabled unless effectively pixel your site for Woocommerce.

    After desable this extension because I am not actually using Woocommerce and actualized the cookies list in the complianz extension, I confirm that the error message no more appears.

    Thank you for your help and your quick answers.

    Thread Starter chowolo35

    (@chowolo35)

    I close the topic because the problem is solved

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘console log frontend error Cannot read properties of undefined’ is closed to new replies.