Richard

Hi Jay,

Happy New Year!

1. I’m not sure how the plugin tracks views, but it doesn’t seem to set client side trackers. The scanner crawled all 175 pages without finding anything and I just double checked by browsing the website. There seem to be no cookies in use at all.
2. The images fail to load because the of an error. This is caused by the Cookiebot script being loaded twice.
3. You shouldn’t implement the script using a widget when you use the plugin, this will cause errors or unexpected behavior at least (see previous).
   I can see on the page the script is indeed implemented twice, and it does cause the jQuery script to not load. I suggest removing the script implemented by the widget.

Hi Jay,

There used to be an issues with both Elementor and Divi editors, but these should be resolved in the latest version of our plugin (3.4)

Is there a way for me to see this issue somewhere? a staging area or an orphaned page perhaps?

Hi @ligoline

Could you provide some links to these websites? If you’re uncomfortable with sharing this information an open forum, you can send the links to [email protected]

Hi @ligoline

Which website had these issues? We would like to do some tests to see what causes these issues.

Hi Jay,

The font-color is likely overruled by the stylesheet of your website. This also explains why this doesn’t happen during the preview.
I just visited your website, but didn’t notice anything strange.

Both the text color and navigation seemed to be working as one might expect. Did you solve the issue in the mean time?

Hi Maren,

As with any button or link, a plugin can’t create those for you. Afterall how would it know where to place them on your page? Our plugin only inserts the script, with your settings into the header of each page.

You’ll need to create a link as you normally do, only now it will issue a command instead of following a link. If this is an insurmountable task, then I’m afraid you won’t be able to create the link you want.

Hi Inga,

You can’t do this yourself, but I can “consolidate” dynamically named cookies for you, to avoid this behavior. I’ll have a look at this and set it up for you.

Hi Marco,

Due to the way the automatic cookie blocking script processes the page, some delays are unavoidable.
We are looking into how we can optimize the process to make the delays less significant though.
If the delays are unacceptable, you may consider using the manual cookie blocking mode, it’s not as easy to implement, but there will be no delays.

Hi Maren,

You can simply create a button or a hyperlink using the following command: Cookiebot.renew()

For example: <a href="void(0)" onclick='javascript:Cookiebot.renew()'>Renew your consent</a>

• This reply was modified 5 years, 2 months ago by Richard.
• This reply was modified 5 years, 2 months ago by Richard.

Hi Claudia,

The Cookiebot script is implemented twice, once on line 2 (by the plugin) and again on line 42(manually added perhaps?. This second occurrence can (and should) be removed.

The caching times have been reduced in the past, to ensure changes and fixes become available to users as soon as possible.
Although this can lead to slightly slower loading times on return visits, this does ensure that the Cookiebot script works as intended.
Furthermore, both uc.js and cc.js are relatively small (14.2 kb and 28.4 kb respectively), caching these scripts wouldn’t offer such an advantage to justify caching to scripts for an extended period.

The non-passive event listener to a scroll-blocking “wheel” event is used when you choose the overlay type banner, this applies an overlay and disables scrolling, to “force” the user to interact with the banner, instead of simply ignore it.

Hi C?me,

Judging from your video, the script actually does what it’s supposed to. You see, Google Maps sets marketing cookies, so to be able to use Google Maps, consent is required.

If the map is essential for the service your website is meant to provide, you can assign the “necessary” category to the cookie this script sets in the manager. This will allow the script to run without prior consent.

If the map is not essential, I would recommend using placeholders. This will make the site look normal, and you have a second chance to get consent to marketing cookies.

Hi @golfball-uhu,

The banner can’t be displayed if the script isn’t present on the page. I suspect that you’ve added Cookiebot multiple times, perhaps once using the WordPress plugin or Google Tag Manager and once by adding it to the header.
This is known to cause errors, particularly if one implementation uses the automated blocking functionality and the other uses manual cookie blocking.

Please make sure that you only implement the Cookiebot script once (I suggest using the plugin).

In regards to the scans, you don’t need to have our banner on the page to be able to scan your website. Scans will happen as long as the domain is added in a Domain Group in the Cookiebot Manager.

In the second last update of the Cookiebot plugin (3.20), some temporary fixes were released specifically for issues with certain WordPress plugins (like Divi and Elementor). However, when these plugins themselves were recently updated, the issues resurfaced.
Our developers are working on a more permanent solution, but could give no estimate on when we can expect this to be available.

The best course of action is to temporarily switch to manual cookie blocking mode while editing, and switching back to automatic cookie blocking right before publishing.
We apologize for this inconvenience.

Hi @modena1989,

In the newer versions of the Cookiebot plugin, you have the option to disable the Cookiebot script in the WordPress backend.
Is it possible you haven’t done this (yet)?

Hi @chris244,

I’m sorry to hear our solution wasn’t working out for you.
Cookiebot can be implemented in a number of ways, depending on which method you used there are a few different ways you can go about removing it:

• Remove the Cookiebot WordPress plugin if you have it.
• Check if you have plugin that inserts code into the header of your pages, and remove the Cookiebot script if it’s present.
• If you implemented Cookiebot using Google Tag Manager, remove the tag.

The cookies you mention, _tltpl_286582 and _tltpl_286640 aren’t set by Cookiebot, your new Consent Management Solution may be able to point out where these come from.