cookiebot

Alright. If you are using Wordfence it has an option to disable cookies 🙂

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

Hi @cliffuk,

The cookie is probably coming from one of your plugins.

Which plugins are you using?

A google search for wfvt returns the “Wordfence” plugin. Are you using this?

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

Hi Aaron,

Thanks for reaching out, and thanks for your input!

If we can’t offer something that is always guaranteed to work, we wont implement it in the Cookiebot plugin.

It is not guaranteed that every plugin or theme is using wp_enqueue_script, therefor, Cookiebot cannot guarantee its users compliance, if we choose to take that path.

We are experiencing a lot of frustration from WP users, which is why we have created a public Github repository, where we are developing “addons/plugins”, which will integrate Cookiebot with various plugins. This is for the community, and as a member of the community, you are welcome to create pull requests for your favorite plugins.

Bare in mind that the Cookiebot plugin itself is giving the users the ability to become compliant, but it is not our responsibility to fix every other plugin so that it works with Cookiebot, nor is it our responsibility to make WP Core compliant. WP Core is actually working on that right now.

The Github repo was created today, and we are ready with our first integration to MonsterInsights. In the near future, we will extend it with integrations to other plugins, so do you have anything on your wish list?

Right now there is no documentation, but all you have to do is add the addon/plugin to your plugins folder and activate it.

https://github.com/CybotAS/CookiebotAddons

[ Signature deleted ]

• This reply was modified 8 years ago by cookiebot.
• This reply was modified 8 years ago by cookiebot.
• This reply was modified 8 years ago by Jan Dembowski.

Hi @cliffuk,

Thanks for reaching out!

It’s not enough just to install the plugin. All cookie-setting tags on your website have to be marked up according to our guidelines at: https://www.cookiebot.com/goto/help/

Where it becomes tricky is marking up script tags that come from plugins that you’ve installed. We’ve already answered a similar question on how to locate tags from other plugins and mark them up (and how to verify if you are compliant):

https://wordpress.org/support/topic/where-are-the-script-tags/

A disadvantage with the approach is that your changes will be lost when you update the plugin. We’ve made it easy for other plugin-developers to integrate with Cookiebot, however the community/users should ask the plugin developers if they would like to make this integration, so you guys can stay compliant.

As we are drowning in WP support requests, we are currently making videos showing how to implement Cookiebot correctly on any website, but also on WP. Moreover, we are considering creating “addons” for the most popular plugins, so that our users can use them together with Cookiebot. This is not an optimal path for us, as we have to maintain these addons whenever the other guys update their plugins. However, making websites compliant should not only rest on our shoulders, It is a task that community should help each other with.

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

hi @neiljordan,

Thanks for reaching out!

We’ll look into it and get back to you once it’s resolved.

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

Hi @tallsam,

Thanks for reaching out!

Cookiebot focuses on online-tracking. Once a month Cookiebot will perform an automated cookie audit by scanning your website for cookies (HTTP/Javascript cookies, HTML5 Local Storage, Flash Local Shared Object, Silverlight Isolated Storage, IndexedDB, ultrasound beacons, pixel tags) and generate a cookie declaration with descriptions on every cookie found on your website.

Our plugin does not manage other aspects of GDPR compliance, such as giving the users the ability to see what data you have stored for them. The WP Core team is extending WordPress to facilitate this. You can have a look at the WP issue tracker, to see what’s currently in development, what’s done and when it will be released:

https://core.trac.wordpress.org/query?status=!closed&keywords=~gdpr

Moreover, you could have a look at some other plugins that are additions to what WP Core is developing, and which work nicely with Cookiebot. One such plugin is WP GDPR:

https://wordpress.org/plugins/wp-gdpr-core/

Thank you for the input on our pricing model. We’ve given the model a lot of thought, and weighed in the pros and cons. No matter what the model looks like, there will always be someone who is unsatisfied.

[ Signature deleted ]

• This reply was modified 8 years ago by Jan Dembowski.

Hi @idansh,

Thansk for reaching out, and thanks for using Cookiebot!

1) Will my first free website will turn into paid one?

If your website is under 100 pages, then it will not turn into a paid one.
See also: https://cybot.uservoice.com/knowledgebase/articles/1851772-my-subscription-has-been-changed-from-a-free-subsc

2) If my blog is only three pages, can I open a second free account or this isn’t allowed?

Our FAQ at https://www.cookiebot.com/en/pricing/ states that:

Our prices are per domain and you must have one subscription for each of your domains. It is not possible to combine e.g. 2 small websites with 10 subpages each into one Premium Small subscription or into one Free subscription.

3) Does your plugin automatically block cookies or I need to configure the tags for the script manually and for all the other scripts that generate cookies? I am asking this, because from my experience, the non-wordpress plugin, the script I’ve embedded. I needed to manually configure thing myself. I am a developer, so it’s not a big issue, but I’m sure many people are not developers, and they will definitely have problem doing it.

Currently you have to do it manually for all tags, including tags coming from other plugins. We’ve made it possible for other plugin developers to integrate with Cookiebot easily:

The easiest way for at developer to implement Cookiebot support is following to add a check for Cookiebot where tags are outputted to the visitor. This can be done following way

$scriptTag = ”;
if(function_exists(‘cookiebot_active’) && cookiebot_active()) {
$scriptTag = ‘<script’.cookiebot_assist(‘statistics’).’>’;
}

So if you’d like your plugins to stay compliant, you could reach out to the developers, and ask them if they would like to support Cookiebot. This also means, that you would not have to manually update the plugins on new releases.

[ Signature deleted ]

• This reply was modified 8 years ago by cookiebot.
• This reply was modified 8 years ago by Jan Dembowski.