Richard

Hi @angeloarlotta,

I looked up the support ticket you referred to in your message. The screenshot you shared quite clearly shows the problem. I suspect you can get the declaration to be displayed in a more optimal way by added some rules to your stylesheet. For example:

.CookieDeclaration p {
    font-size: 6pt;
}

Hi @ciromuto

This isn’t an actually error, it’s just a notification that the tcString indicates that Google Ads Sense wasn’t consented to by a user.
This will happen if a user opts out of Marketing cookies, or specifically disallowed Google as a vendor.

• This reply was modified 4 years, 6 months ago by Richard.

Hi @ciromuto,

1.1 Errors occur when a returning user has a TC string older than August 1st. Forcing consent renewal in the Manager will fix this issue.

2.1a Errors occur when Google Ad Sense executes before the consent string has been generated (which happens when the users submits his/her consent). This is likely due to categorizing the cookies set by Google Ad Sense as anything other than Marketing.

Hi Luca,

The latest version should be 3.7.1. You’ll be able to see which version you currently have by inspecting your plugins page (/wp-admin/plugins.php).

Hi Luca,

There seems to have been a bug in the last release of the plugin. This is currently being worked on.
In the meantime, if you download and install the currently newest version of the plugin, the error shouldn’t occur anymore.
We apologize for the inconvenience.

Hi @danitron81,

Just to follow up, everything appears to be in order with the scans for farmaciaalfonsomonllor.com and the cookies are displaying correctly in the Cookiebot banner as well. If you experience any issues, do reach out again.

Hi @pernillerenleff,

It looks as if the scan completed today has detected the cookies in use on type1.dk – they are also displayed on your Cookiebot banner. If you are experiencing any issues we cannot see from here, please do reach out again.

Hi @jlindeborg,

It’s difficult to give a qualified explanation with the information you provide.
Would you mind sharing the domain you’re trying to implement Cookiebot on?

If you prefer not divulging this information on a public forum, you can write to [email protected]

Hi Mark,

You probably need to manually delete the Cookiebot plugin folder.
I suspect this somehow failed when you deleted the plugin, and now complains that it can’t save where it wants to.

Hi Jaime,

Regarding YouTube no-cookie, despite the name suggesting the opposite, that still sets cookies. However, if you can disable cookies by adding a parameter, the scanner should recognize that no cookies are set, and won’t flag them or attempt to block the resource.

You can always “ignore” the resource, but please make sure that you don’t accidentally set cookies without consent.

Hi Jaime,

I wasn’t aware that adding ?dnt=1 disables cookies.
Theoretically, this indeed works and the iframe doesn’t set cookies, our scanner won’t flag the iframe as a source of cookies, and won’t attempt to block it.

Should this not be the case though, and you prefer to use that setting and want to override Cookiebot’s “judgement”, you can add the following attribute to the iframe: data-cookieconsent=”ignore”.
Be careful when using this attribute though! Any element with it can set cookies without consent and using it arbitrarily on scripts can cause reference errors.

Hi @webarkitekterne,

Since I don’t know which domain is affected, I’m going to make some assumptions based on known issues.
Using the POST method to pass form information doesn’t work in Internet Explorer when using auto blocking, due to IE not supporting the mutationObserver method.

Here are some solutions, if this is indeed the issue you’re affected by:

1. Use GET instead of POST to pass data
2. Use manual blocking mode instead of auto

Hi Lars,

If they cookie in question is unclassified, the Cookiebot script won’t know what to do with it and flag it with “Blocked until accepted by user: No”.

If you assign the cookie a category and perform a new scan in the Manager, the warning should go away.

• This reply was modified 4 years, 10 months ago by Richard.
• This reply was modified 4 years, 10 months ago by Richard.

Hi @andygoe,

I can’t seem to replicate the behavior you describe, even in IE 11.
Would you happen to have a screenshot?

Hi @metalguru69,

Thank you for the kind words! Much appreciated.