Antonio Candela

Hello @mloe123 ,

Their developer still has not answered me on this topic. Here’s the link to their support forum: https://wordpress.org/support/topic/php-warning-with-addtoany-share-buttons-and-complianz.

For the time being, I will close this thread, as we have done everything in our power. As soon as their developer answers us, we’ll comment here.

Best regards,
Antonio

Hi @tdsm ,

Thanks for reaching out.

That API call to api.onsleek.ai is not part of our plugin. It’s likely being triggered by another plugin or your theme.

Our scanner crawls all the pages and scripts active on your website, which is probably why you’re seeing that error message during the scan process. If that third-party script is failing, it might interfere with the rest of the scan.

As a troubleshooting step, we recommend temporarily disabling the plugin or feature responsible for that API call and then running the cookie scan again. This will help determine if it’s the source of the categorization issue.

Let us know what you find.

Best regards,
Antonio

Hello @shustus ,

Thank you for your feedback.

When the Website Scan is disabled via the API menu, Complianz automatically falls back to the local iframe scanner (the previous scanning method). This is expected behavior.

Because the local scanner works by loading your site inside an iframe, its results can vary depending on factors like browser or server caching. That’s why you may sometimes see slightly different cookie counts (e.g., 100/120) or cookies from plugins you’ve previously used or that left cached assets behind.

I hope this clears things up! When using the local scanner, it’s usually best to run the scan in an incognito window to get the most accurate results. That said, I’ll update you as soon as we have the branch ready with the possible fix. Thank you for your patience.

Best regards,
Antonio

• This reply was modified 8 months ago by Antonio Candela. Reason: typo

Hello @nummu4 ,

Thank you for reaching out.

I checked your setup, and it looks like the same Google Analytics tag is being inserted simultaneously by Complianz, Google Analytics for WooCommerce, and a custom integration about the Consent Mode v2. This overlap can easily lead to redundant or conflicting tag behavior.

In this case, it would be best to let Google Analytics for WooCommerce handle all tracking by enabling the integration in
Complianz > Integrations > Plugins > WooCommerce Google Analytics Integration.
When this integration is active, the fields in Statistics Configuration will be hidden, and GA for WooCommerce will be the only plugin inserting the gtag script. This will remove the redundancy and ensure proper event tracking.

To properly test this, you should try with Complianz disabled, as the Google Analytics tag is being added directly by the external plugin. I tested the tag myself using only Google Analytics for WooCommerce, and it fired correctly.

With that said, regarding the main issue: tracking specific events; I would recommend contacting the support team of Google Analytics for WooCommerce, as they can best assist you in making sure your eCommerce events are tracked properly.

Best regards,
Antonio

Hello @klaassemanoah,

Thank you for reaching out.

You can use the attached snippet, it will allow both the Cookie Policy and Privacy Policy links to open in a new tab. If you only want the Privacy Policy to open in a new tab, simply remove the Cookie Policy part from the code.

Here’s the Gist:https://gist.github.com/tonai126/5df78817d54abadfbc28ab1a38367dc9.

I hope this helps!
Best regards,
Antonio

Hello @petadol ,

Thank you for reaching out and for the report. Could you please explain how exactly you reproduce this error? I’ve checked the site and, after accepting the banner, there are no errors showing in the console.

I also noticed that the banner CSS is not up to date, so it’s necessary to save the banner again in the wizard and clear the cache. That should fix the styling.

That said, I also see that you are using Complianz Premium. Due to WordPress.org rules, we cannot provide support for commercial plugins here. Please contact us directly through our website support form so we can assist you further. For this reason, the thread will be closed.

Thanks for your understanding.

Best regards,
Antonio

Hello @mloe123 ,

Thank you for reaching out.

This specific issue with translation loading was actually addressed and fixed in the Complianz plugin’s code several months ago. However, it can sometimes reappear if another plugin on your site triggers certain actions earlier than expected during the WordPress request, which might cause this particular problem to resurface. Following some reports, we’ve also discovered other causes for this issue reappearance, and our team is actively investigating and resolving them.

So, unless you’re running an outdated version of Complianz (in this case, my suggestion is to update the plugin), I recommend you try a few troubleshooting steps:

• Disable wp_debug temporarily (if it’s currently enabled) to see if the notices disappear.
• Deactivate all other plugins on your site, then reactivate them one by one, checking after each activation to see if the notice reappears. This will help you pinpoint the plugin that might be causing the conflict.

If you need further assistance or have any other questions, we are at your disposal.

Kind Regards,
Antonio