rapportdesign

That’s great… Thanks!

OK, well it seems odd that it didn’t automatically downgrade in time for the following month, but did the day I looked into it.

I ran a manual scan from within my Cookiebot account the day it downgraded, so it’s likely that was what triggered it.

Our subscription downgraded shortly after making this post, so I’m guessing it was either a coincidence or someone spotted this post and manually downgraded us.

Either way, my issue has been resolved.

My issue with Twitter is that I can’t see the cookie being set, even after consent.

I thought marking the scripts up with the data-cookieconsent attribute, just categorised the cookie files, allowing the user to choose which ones to accept.

I don’t understand how this will allow me to see cookie files being set in the browser, which I’m not already.

Anyway, I’ve tried it (including the type=”text/plain”) and I can now see a personalization_id cookie file is set, which may not be directly related to this change, as I haven’t seen details of this before.

Still, no sign on the cookie files originally discussed… https://snag.gy/0aIn24.jpg

That’s working great now… Many thanks for taking a look!

The Twitter cookie is on the Home page and there is a Twitter feed.
The problem is, even after consent, the cookie file isn’t set.

“It is also important to understand that many cookies are so-called dynamic cookies. These – unlike ‘classical’ http/Javascript cookies – are not being set when the website is loaded. They are being set during the visit depending on the user’s behavior on your website.”
https://support.cookiebot.com/hc/en-us/articles/360004269614-Why-does-your-scanner-find-cookies-and-trackers-that-I-cannot-myself-find-on-my-website-Where-do-they-come-from-

I meant to mention in my last post, it would be great if the report could indicate the user simulated action, which tool place to detect the cookie.
I realise this is probably asking a bit too much, but it would be a good feature to consider.

Thanks for the link to that article…

In a previous post, I’d asked who was to blame if a cookie file that’s being set by a plugin, had been blocked by Cookiebot until consent, but due to a glitch in a plugin update, the cookie file was now getting set again without consent. The answer was the site owner.

Due to almost daily plugin updates, this seems very difficult to keep on top of.

I’ve recently discovered such an issue with Add To Any Share Buttons, so it does happen.

The article you’ve just provided says “The browsers of today are simply not advanced enough to see all the cookies and trackers being set.”, yet the video here shows using the browser to identify if you’ve correctly marked up scripts for prior consent… https://www.youtube.com/watch?v=MeHycvV2QCQ

Now that I know there are cookie files being set and the tools used for checking them, aren’t up to the job, I can’t see how the blame can possibly be put onto the site owner.

Surely a piece of code setting the advanced cookie, which can only be detected by a scanner that has been developed and refined over the past 6 years, is the responsibility of the person who produced that code? I realise they may have terms that cover them, but I still don’t understand how site owners can stop themselves from being liable.

Again, I’m not venting my frustration at Cookiebot. I realise you’re dealing with an awkward area and are offering one of the best solutions out there, but I’m sure you can see why this is frustrating from a website owners point of view.

My report has come back and the Zoho cookies aren’t necessary, so I’ll be contacting them now.

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.

Rocket…
https://www.dropbox.com/s/vg5ip2zt5ncu4b0/wp-rocket-settings-2019-03-14-5c8a2cea29c03.json?dl=0

Plugins…
https://www.dropbox.com/s/apgijfgxeoacuvt/Gov-Data.pluginlist.2019-03-14.txt?dl=0

Thanks!

Thanks, I’ve sent details.

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?

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

Many thanks for the quick reply.

To be honest, I hadn’t even noticed the options panel.

The path to the .htaccess file was already completed as a placeholder.
I replaced it with the same value, including .htaccess, as it specifies the full path AND filename.

I removed my redirect and re-added it, but there was no change to my .htaccess file. I’m pretty sure the permissions are OK, because WordPress, WP Rocket and Wordfence are all writing to the .htaccess file OK.

I repeated the process, but without including the .htaccess in the URL path, but it still didn’t work and just converted back to a placeholder.

Anyway, I’m not expecting you to find time to investigate further.
I understand this isn’t a premium plugin.
If you’re interested in knowing what’s going on and would like to see for yourself, I can provide logins.
If not, I’m OK with sticking to directly modifying the .htaccess file.

The 20% will help cover the time I need to spend regularly monitoring each site.

For those that want a quick insight into the book you’ve recommended, they may find this link useful. https://www.youtube.com/watch?v=Vo6K-bPh39M

Apologies if my frustration has felt like it’s been directed at Cookiebot.

I appreciate the benefits of this service and understand the costs associated, but it’s a tough one to convince the client.

Thanks for your time.