Antonio Candela

Hi @presidentnickson ,

This issue was resolved several months ago. If you have updated the plugin, you should no longer experience this problem. If the issue persists despite using the latest version, we kindly ask you to open a new thread so we can investigate the specific cause in your setup.

From our side, the bug has been fixed. If you are still seeing the text domain notice, it’s very likely caused by an external plugin or integration that is triggering translations too early.

In the new thread, it would be very helpful if you could describe your setup in more detail so we can assist you further.

Best regards,
Antonio

Hello @cleophems ,

Thank you for your detailed message and for the information you’ve already provided.

Regarding the PHP notice related to the early loading of translations: we’ve addressed this issue months ago in our updates, so it’s likely being caused by a third-party plugin that’s forcing translation loading too early. Could you let us know which other plugins are currently active on the site?

Additionally, I checked the website and noticed that while the assets load, the main JavaScript file for the banner does not appear to load.

Could you please try temporarily deactivating all other plugins and leaving only Complianz active, just to see if the banner starts working? That would help narrow down the root cause quickly.

Also, I’d like to confirm that the versions you’re using: Complianz 7.4.1, WordPress 6.8.2, PHP 8.1.32, Hello theme from Elementor, are all compatible with each other, so that should not be a source of the issue.

Let me know how it goes!
Best regards,
Antonio

Hello @julie2009 ,

Thank you for reaching out.

If you prefer not to show Section 6 (“Placed Cookies”) of the Cookie Policy, you can manually remove it by editing the document directly. We have a guide that explains how to do this step by step: https://complianz.io/editing-legal-documents/.

But please note: manually editing the document will cause it to lose synchronization with the Complianz Wizard, meaning it will no longer update automatically when changes are made.

I hope this helps.
Best regards,
Antonio

Hi @cstoll ,

Thanks again for your follow-up.

Technically speaking, the double Matomo injection is correct in this case, since the course page is effectively embedded as a full page, which results in Complianz (and thus Matomo) being loaded twice.

What you can do to prevent this from affecting your stats is to exclude those specific paths (where this double injection occurs) directly within Matomo. This way, data from those pages won’t be included in your analytics reports.

I hope this helps.
Best regards,
Antonio

Hello @wokal ,

Thank you for reaching out and for the detailed explanation.

By default, Complianz does not block Google Tag Manager itself, as this behavior is compliant with current GDPR regulations. Instead, GTM serves as a container, and the individual tags inside it should be triggered based on the user’s consent preferences.

To achieve this, you can set up consent-based triggers within Google Tag Manager. This way, each tag will load only if the user has given consent for the corresponding category. We explain this setup in more detail here: https://complianz.io/definitive-guide-to-tag-manager-and-complianz/.

However, if your goal is to load the entire Google Tag Manager container only after consent is given (as you mentioned) you can follow this alternative guide, which explains how to delay GTM loading entirely until statistics consent is obtained: https://complianz.io/how-to-set-google-tag-manager-after-consent-and-is-it-needed/.

I hope this helps, we remain at your disposal!

Best regards,
Antonio

Hello @vanektomas ,

Thank you for reaching out.

This issue should now be resolved. Could you please try clearing your cookies and syncing again from the Complianz dashboard in Wizard > Consent > Site scan / cookiedatabase.org? The “Pirated software” service should disappear from the cookie list afterwards.

Please let us know if it persists.

Best regards,
Antonio

Hello @nashiram ,

Thanks for reaching out.

It sounds like there might be an issue with the REST API or permissions on your site. Could you open the browser console and then visit the Complianz page in your WordPress dashboard? If you see any errors there, please send us a screenshot, that would really help us identify the problem.

Please let us know.

Best regards,
Antonio