CookieYes Team

Hi @sonjoe

Greetings from CookieYes!

We’re sorry to hear about your experience and the difficulties you encountered with our plugin. The issues you face could be caused by conflicts with other plugins, themes, or server configurations. We’d love to investigate this further and help you resolve it. Please raise a query via the?support forum by including details about your setup, such as the WordPress version, active plugins, and any console errors.

Hi @supportdelfino

You have not added the backtick?`?before?.cky-btn-revisit-wrapper?and after?!important;}

Hi @ivancza

Please check the working after excluding the CookieYes script from the JS optimisation.

Hi @leemon

We couldn’t replicate this warning while testing our plugin on WordPress 6.7

Could you please confirm whether you are using the latest version of our plugin?

Hi @burlingtonpress

Greetings from CookieYes!

This feature is available only in our paid plans. You may contact our support to learn more about it, as this forum can only be used to discuss the free version.

While using Google’s advertising products, such as Google Analytics or Google Ads, Google does mandate the use of GCM to help manage consent for cookies and tracking in line with privacy regulations. So, while it’s not mandated by law, GCM is an important tool for ensuring compliance with Google’s policies, especially if you’re using their services.

Hi @fatcacky

Greetings from CookieYes!

It appears the issue is due to our plugin categorizing certain cookies, such as those used by Typeform or other embedded content, as “unnecessary.” When the plugin blocks these cookies by default, it can prevent specific site elements, like images or embedded forms, from loading properly.

To resolve this, you can adjust the settings to allow these cookies:

• Review Cookie Categories: Go to CookieYes > Cookie Manager > Cookie List and check the cookies being blocked. Look for any related to images, Typeform, or other essential functions.
• Reclassify Necessary Cookies: If you identify cookies essential for your site’s functionality, you can reclassify them as “necessary” so they’re allowed by default. This way, critical functionalities won’t be blocked by the plugin.

When reclassifying cookies to the “necessary” category, please ensure they don’t store any personal information about visitors. Also, consider seeking legal advice to confirm you’re meeting GDPR and other relevant compliance requirements.

Please let us know if you can try reactivating the plugin and making these adjustments. We’d be happy to assist with further steps if needed.

Hi @leemon

Greetings from CookieYes!

Thank you for bringing this to our attention!

Since WordPress 6.7 is still in RC4 and not yet officially released, we haven’t released a compatibility-tested version of our plugin for it. However, our team is already reviewing this change to ensure compatibility once WordPress 6.7 is launched.

Thank you again for helping us improve the plugin. Please feel free to reach out if you have further questions in the meantime.

Hi @ivancza

Greetings from CookieYes!

Could you please share the URL where this issue is happening, along with the ad blocker being used? This will help us investigate further and provide a more specific solution.

We’re currently working on a fix for this issue, which will be included in our next release. For now, we’ll mark this thread as resolved, but please feel free to open a new thread or follow up here if you have any further questions or need assistance after the update.

Hi @nblund

Greetings from CookieYes!

Currently, our plugin does not automatically provide translations for individual cookie descriptions. However, you can add these translations manually within the plugin. To do this, go to CookieYes > Cookie Manager > Cookie List, select Danish from the “Edit content in” dropdown, and then edit each cookie to add the Danish translations.

If you need further assistance, please don’t hesitate to reach out!

Hi @123nadav

FDBR is similar to the rest of the state privacy laws of USA. It is stricter in the sense that the other laws requires a revenue of a few hundred thousands or a couple of million in global gross revenue to have the privacy laws applicable to them, while FDBR has set that limit to $1billion minimum. This means that the law will be applicable mostly to MNCs that have revenue more than a billion in a year. However, other provisions are more or less the same and when it comes to consent mechanisms, a CMP with an option to provide opt-out would be compatible with the law.

Hi @tutumu

This thread has been inactive for a bit, so we are going to mark it as resolved now. Please feel free to open a new thread or follow-up if you have any further questions or still need help.

Hi @supportdelfino

This thread has been inactive for a bit, so we are going to mark it as resolved now. Please feel free to open a new thread or follow-up if you have any further questions or still need help.

Hi @cvioletis

This thread has been inactive for a bit, so we are going to mark it as resolved now. Please feel free to open a new thread or follow-up if you have any further questions or still need help.