• Resolved nataliactivex

    (@nataliactivex)


    Hello,

    I have an error on the site when i activate de plugin:

    “Uncaught ReferenceError: google is not defined”

    with this error some parts of the site stop working.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @nataliactivex,

    This sounds like a dependency error when a Google service is blocked. Can I have a look at your website, so I can look at the details?

    regards Aert

    Thread Starter nataliactivex

    (@nataliactivex)

    Hi,

    Yes, this is the website: https://demo.veigamotos.pt/

    as you can see this page has errors in the images.
    https://demo.veigamotos.pt/autos/cfmoto-c-force-1000-overland-duplicate-1/

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @nataliactivex,

    Can you disable the Google Maps integration under Complianz > Integrations > Services, as well as the Advanced Custom Fields integration under Complianz > Integrations > Plugins? This should resolve the error.

    The reason why it happens is that Complianz is configured to block the Google Maps API on your site before the visitor consents to the use of Marketing cookies, but there is a script from your theme, “scripts.js”, which tries to use the Maps API while it is still blocked.

    That is what causes the error: and because the “scripts.js” file of your theme contains more than just the Google Maps code this error may affect other theme functionality (such as sliders) as well.

    If you would like to block your theme’s Google Map implementation prior to consent from the visitor, your theme developer could split up the Google Map functionality into a separate JavaScript file, so that Complianz can block the Maps code specifically, without affecting other theme functionality included in the “scripts.js” file.

    Kind regards,
    Jarno

    Thread Starter nataliactivex

    (@nataliactivex)

    I have already disabled the option but still with error

    Plugin Contributor jarnovos

    (@jarnovos)

    Hi @nataliactivex,

    Could you disable the Advanced Custom Fields integration as well? It’s located under Complianz > Integrations > Plugins.

    Kind regards,
    Jarno

    Thread Starter nataliactivex

    (@nataliactivex)

    Already did that… Dosent work.

    Plugin Contributor jarnovos

    (@jarnovos)

    Hello @nataliactivex,

    I still see that the Google Maps API is being blocked as a result of the ACF integration being activated under Complianz > Integrations. Screenshot attached.

    Any caching plugins that may need to be cleared upon making these changes, before they are reflected on the front-end?

    If there are no more integrations active in Complianz that result in the Google Maps API being blocked, the issue should disappear.

    Kind regards,
    Jarno

    Plugin Author Aert Hulsebos

    (@aahulsebos)

    Hi @nataliactivex,

    I see this in the page source:

    <script type="text/plain" data-service="acf-custom-maps" data-category="marketing" src='//maps.googleapis.com/maps/api/js?key=AIzaSyAzNSaK6s4IQOdCHJewwPaL10QtmE6Yfco&ver=6.0.2' id='google-maps-api-js'></script>

    It seems ACF is still blocked. With https://demo.veigamotos.pt/?cmplz_safe_mode=1 it’s fine, and the only remaining integration besides Analytics is ACF.

    Could you try again?

    Which Google Maps integration/plugin are you using?

    regards Aert

    Thread Starter nataliactivex

    (@nataliactivex)

    I had to remove the integration of the Elementor and Advanced Custom Fields.
    It works now.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘error in plugin’ is closed to new replies.