These errors can be caused by a wide range of conflicts. It can be due to PHP version, memory, plugin compatibility, or your theme. To find out what might cause this, WordPress has released a handy tool to figure out what might cause these errors.

To get a step-by-step guide to pinpoint the issue, please read this article. If you’re confident you know what might cause this, or the error explains the issue:

Please check our documentation and contact support if needed.

If you have finished the wizard, Complianz will enable the cookie blocker, to block third-party services and add a placeholder. This might result in a malfunctioning form or YouTube integration for example if the implementation is not a default or expected.

If you know which service this refers to you can disable the integration under Complianz -> Integrations. If you’re not sure, you can start with disabling all Integrations and enable them one by one to see which one is the culprit.

Next step:

If you figured out the issue, please contact support if we need to have a look or look at the documentation if the subject has already been described.

To start debugging this issue, please visit this article, which explains the minor issues that might cause this. Clearing cache should always be a first when installing a plugin that affects the front-end of your website.

There are 2 likely issues that might cause custom CSS not to work.

Either your theme or other plugins interfere with your CSS. Or your browser, and/or website still has an old cache that should be cleared.

Besides using the correct CSS handles, these two should clear most issues. If that didn’t work, please ask support.

For CSS tricks, have a look at our collection of Custom CSS here.

If services are not blocked correctly, the integration is either not enabled, or there’s no specific integration for your service, or type of implementation.

Please see if you can enable the service under Integrations -> Services, or use our script center to manually block your service.

For inline scripts you can use shortcodes as well.

If you want to do a feature request for integration, please follow this link.

If you think analytics is not configured correctly, please follow these articles to check if you have implemented analytics correctly.

• The definitive guide to Tag Manager
• Are your IP addresses anonymized?
• Duplicate Implementation of Analytics
• Analytics configuration for GDPR

The cookie scan results might differ from what you expect. This could be positive, as some cookies and services are installed without your knowledge. If you’re positive something is wrong, read this article to minimize issues during a cookie scan or see what might be wrong.

If you’re using reCaptcha, and it is enabled under Integrations, you might want to have a look at configuring this for your specific form; here are some articles that might help.

• Blocking reCaptcha on Divi
• Elementor, reCaptcha and the Native Form
• Blocking reCaptcha & Editing the Placeholder
• Google reCAPTCHA and the GDPR: a possible conflict?

Complianz integrates with WPML & Polylang, and other translations plugins as well. For the aforementioned, you can use this article to troubleshoot your translations. To configure Complianz correctly, please visit:

• Troubleshoot translations
• Configure for WPML
• Premium translations are missing
• Configure for Polylang

1. Login to your FTP client, and search for your WordPress installation root.
2. Go to /wp-content/plugins/ and change the name of the Complianz folder. This will deactivate Complianz, and all features.
3. Read our article on “A fatal error” to debug the issue and contact support.