antoiub

Hello @braino ,

We have released the fix on GitHub first. You can download it here: https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/fix/translations-wp67.
You can install the .zip file by going to Plugins > Add a New Plugin > Upload Plugin, and then clicking Install Now.

Please make sure to update your translations first in Dashboard > Updates > Translations.

Please let us know.
Regards.

Hello @boosterbast ,

We have released the fix on GitHub first. You can download it here: https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/fix/translations-wp67.
You can install the .zip file by going to Plugins > Add a New Plugin > Upload Plugin, and then clicking Install Now.

Please make sure to update your translations first in Dashboard > Updates > Translations.

Please let us know.
Regards.

Hello @ilgrizly ,

We have released the fix on GitHub first. You can download it here: https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/fix/translations-wp67.
You can install the .zip file by going to Plugins > Add a New Plugin > Upload Plugin, and then clicking Install Now.

Please make sure to update your translations first in Dashboard > Updates > Translations.

Please let us know.
Regards.

Hello @dominikzuk ,

We have released the fix on GitHub first. You can download it here: https://github.com/Really-Simple-Plugins/complianz-gdpr/tree/fix/translations-wp67.
You can install the .zip file by going to Plugins > Add a New Plugin > Upload Plugin, and then clicking Install Now.

Please make sure to update your translations first in Dashboard > Updates > Translations.

Please let us know.
Regards.

Hello @desarrolloaviva ,

If the error didn’t go away after disabling Complianz, it’s not a Complianz issue, so I’ll mark this thread as resolved. You might fix this issue by checking the tags inside your GTM container. Usually, the issue comes from there. I tried to use your GTM container on a test site but had no luck.

I hope this helps with your further troubleshooting.

Hello @maylisbesset22 ,

In this case, you can reach out to them, explaining that you are getting 504 errors when you try to whitelist wp-json/complianz/v1/, and ask if they can check if this issue is hosting/server-sided.
This issue is limiting the capabilities of the plugin.

I hope this helps.

Hello @domov ,

Thank you for reaching out.

Yes, it’s possible. Please check out this guide on our site: https://complianz.io/cross-domain-cookie-consent/

I hope it helps!

Hello @dominikzuk ,

Thanks for the detailed feedback. We are aware of this, and we are going to release an update soon.

Hi @ilgrizly ,

Thanks a lot for understanding. We are going to release the update soon.

Hello @pissenlit ,

Thank you for reaching out.

The Privacy Sandbox is still in development, and we cannot give you a clear answer as we don’t know much ourselves, unfortunately. As soon as we know more, we will provide some documentation on our platforms.

Regards.

Hello @ilgrizly ,

Thank you for reaching out.

I have checked your WP Version, and seems to be the version 6.7. We are currently working on a fix for the newest WordPress 6.7, as they have changed the way translations are loaded. We are now working on a fix to resolve this issue.
We have also put a disclaimer in our support form:?https://prnt.sc/ac0Ipd7WrjJr.

Hello @lookwhoo ,

I’m sorry for your experience. Could you please share with us what problem you encountered? We are here to help.
Looking forward to hearing from you.

Hello @maylisbesset22 ,

Thank you for reaching out.

In this case, you should also request the exception for the Complianz REST API. The URL is the following one: www.site.domain/wp-json/complianz/v1/.

This should solve your issue.

Hello @yodastudio ,

Thanks for reaching out.

Yes, our free version supports translation plugins like WPML. Please check out this guide: https://complianz.io/translate-legal-documents-to-multiple-languages-with-wpml/

Hope it helps.

Hello @dominikzuk ,

I’m truly sorry to hear this. We are currently working on a fix for the newest WordPress 6.7, as they have changed the way translations are loaded. We are now working on a fix to resolve this issue.
We have also put a disclaimer in our support form: https://prnt.sc/ac0Ipd7WrjJr.