Plugin Author
aytac
(@aytac)
Hello @rapportdesign,
Can you clear the cache and try again? If it doesn’t work, can you please give us the plugin version numbers and wordpress version? so we can try to reproduce the issue.
About your other questions, The Types checkboxes are for adding extra layer of control to allow certain cookies. For example google analytics does track users. So to allow that cookie, the visitor will need to check statistics type. Otherwise that cookie will be blocked by the cookiebot. In your case, the addToAny cookies should be allowed when the visitor checks statistics and marketing types.
The placeholder option notifies the visitor to allow certain cookie types to allow a feature. For example, the visitor allows only the necessary cookies after the pageload. Due to that a part of the website/feature will not be visible. With the placeholder option you can notify the visitor that they can see that feature by allowing more cookie types (statistics, marketing and preferences).
Take care,
Aytac
Thanks for the checkboxes explanation… That makes more sense now!
The placeholder seems obvious now you’ve explained it.
WordPress 5.1
Cookiebot 2.2.2
There doesn’t appear to be a Cookiebot add-on version.
I’ve created a screencast because it appears the cookie file isn’t set on the initial load but is set on a page refresh.
Our settings have page refresh unticked… https://snag.gy/4t8LqZ.jpg
You’ll notice from the video that the cookie file is set, whilst the cookie popup is still showing.
https://www.dropbox.com/s/m3b26jp9duipbbz/Cookie%20Issue.mp4?dl=0
Hi @rapportdesign,
Thanks for the video, it clearly shows that third party cookies are set.
Checking the source code on your link, we can see that the script tag for addtoany.min.js is correctly marked up according to Cookiebot guidelines.
However, addToAny loads one more file, page.js, from https://static.addtoany.com/menu/page.js, which is not marked up with text/plain.
We will investigate further and get back to you, with a possible update to the addon.
Plugin Author
aytac
(@aytac)
Hello @rapportdesign,
From the image(https://snag.gy/aSdKhT.jpg), we could pinpoint that you are using an older version than 2.2.2.
Since the version 2.1.0, that settings has an extra option “Remove script untill consent is given”. (https://pasteboard.co/I54Rwk2.png)
Can you please reinstall the plugin and try again?
Take care,
Aytac
As you can see from this video, I’m not going mad. It does say v2.2.2.
https://www.dropbox.com/s/mnbouqidux5o3bn/Cookie%20Version%20Issue.mp4?dl=0
This video shows me removing the plugin and reinstalling it, but the option in your screenshot still isn’t available.
https://www.dropbox.com/s/85sueezf8xdxczr/Cookiebot%20Reinstall.mp4?dl=0
The link below says “If you want the most recent changes get the latest release of the plugin and upliad it to your WP plugins folder”
https://github.com/CybotAS/CookiebotWP
I’ve tried downloading the source code from the link below and replacing the addons directory.
https://github.com/CybotAS/CookiebotWP/releases/tag/v2.1.5
It didn’t make any difference and I’ve now reverted back because the latest release link above, has 2.1.5 in the URL and 2.2.2 is meant to be the latest.
Any ideas?
Hi @rapportdesign
I managed to replicate a similar error in a test setup. However there is still some differences, so I would like to investigate a bit further.
Are you able to provide me with an export of your WP Rocket settings (it seems to be related to this module). You can download the settings here:
/wp-admin/options-general.php?page=wprocket#tools
Furthermore – are you able to sent a video/screenshot/text list of all installed plugins in your installation, so we are able to replicate the setup as precise as possible.
Best Regards,
Johan
Hi @rapportdesign,
We have identified the bug and we are currently testing a fix. You are welcome to test the bugfix – it is included in this development branch:
https://github.com/CybotAS/CookiebotWP/archive/feature/fix-tagging-bug.zip
I will let you know when a release is official.
/Johan
Apologies for the delayed reply, but I didn’t get chance to revisit this yesterday.
That fix seems to have done the trick, so thanks for your time helping me resolve this.
Thanks for reporting the bug @rapportdesign
Next release will include the bugfix.
We’ll go ahead and mark this thread as resolved.
