Title: error in plugin Last modified: September 16, 2022 --- # error in plugin * Resolved [nataliactivex](https://wordpress.org/support/users/nataliactivex/) * (@nataliactivex) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/) * 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](https://wordpress.org/support/users/aahulsebos/) * (@aahulsebos) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16017607) * Hi [@nataliactivex](https://wordpress.org/support/users/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](https://wordpress.org/support/users/nataliactivex/) * (@nataliactivex) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16022234) * Hi, * Yes, this is the website: [https://demo.veigamotos.pt/](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/](https://demo.veigamotos.pt/autos/cfmoto-c-force-1000-overland-duplicate-1/) * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16022309) * Hi [@nataliactivex](https://wordpress.org/support/users/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](https://wordpress.org/support/users/nataliactivex/) * (@nataliactivex) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16022691) * I have already disabled the option but still with error * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16022845) * Hi [@nataliactivex](https://wordpress.org/support/users/nataliactivex/), * Could you disable the Advanced Custom Fields integration as well? It’s located under _Complianz > Integrations > Plugins_. * Kind regards, Jarno * Thread Starter [nataliactivex](https://wordpress.org/support/users/nataliactivex/) * (@nataliactivex) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16037086) * Already did that… Dosent work. * Plugin Contributor [Jarno Vos](https://wordpress.org/support/users/jarnovos/) * (@jarnovos) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16037264) * Hello [@nataliactivex](https://wordpress.org/support/users/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. * ![](https://i0.wp.com/i.ibb.co/0GdTCgb/Schermafbeelding-2022-09-23-om-12-01-46. png?ssl=1) * Kind regards, Jarno * Plugin Author [Aert](https://wordpress.org/support/users/aahulsebos/) * (@aahulsebos) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16037267) * Hi [@nataliactivex](https://wordpress.org/support/users/nataliactivex/), * I see this in the page source: * `` * It seems ACF is still blocked. With [https://demo.veigamotos.pt/?cmplz_safe_mode=1](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](https://wordpress.org/support/users/nataliactivex/) * (@nataliactivex) * [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16043217) * 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. * ![](https://ps.w.org/complianz-gdpr/assets/icon-256x256.png?rev=2881064) * [Complianz - GDPR/CCPA Cookie Consent](https://wordpress.org/plugins/complianz-gdpr/) * [Frequently Asked Questions](https://wordpress.org/plugins/complianz-gdpr/#faq) * [Support Threads](https://wordpress.org/support/plugin/complianz-gdpr/) * [Active Topics](https://wordpress.org/support/plugin/complianz-gdpr/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/complianz-gdpr/unresolved/) * [Reviews](https://wordpress.org/support/plugin/complianz-gdpr/reviews/) * 13 replies * 3 participants * Last reply from: [nataliactivex](https://wordpress.org/support/users/nataliactivex/) * Last activity: [3 years, 8 months ago](https://wordpress.org/support/topic/error-in-plugin-39/#post-16043217) * Status: resolved