theWebalyst

I installed this on a standalone and a multisite today, while hte CISPA blackout is supposed to be active and it doesn’t work.

When I went to settings, it complained about not being able to detect which page the code was on and asked me to save again. I did so, which cleared that error. Cicking test didn’t work on the stand alone website. Clicking test on the multisite displayed a success message (though not the CAT page I was expecting).

However, neither websites are affected and neither display the modal dialogue I was expecting. Doesn’t matter if I’m logged in or not.

URLs are: https://thewebalyst.com (stand alone) and https://wpsites.eu, https://therapy-online.co.uk (multi-site).

This is a shame, I wanted to take part in the CISPA blackout today. Your plugin is a great idea and I hope you can fix this.

Mark

Thanks Bryan, I had no idea that a release candidate would be found on the “Bleeding edge”. I now have 3.5-RC5-23141 installed!

FEATURE REQUEST
How about having the plugin display what is available on the various stream as a banner that updates whenever this changes, and has to be manually cleared. Possible?

A really valuable plugin. Just a bit confusing.

Mark

Just installed 0.96 and this problem persists.

Whenever I hit “Updates” it shows there’s an update of WP available, but it always instals 3.4-latest and I’m getting 3.4 beta 3.

Mark

Thanks Joost, missed that [blush] – that’s great.
Mark

topic now closed

Yes indeed. I’ve updated my blog accordingly:
Recommendations For EU Cookie Law Compliance

Thanks for picking this up and letting me know.

Mark

Interestingly I have not acknowledged the BBC banner or given *any* websites permission, nor cleared the banners yet they have disappeared (at least from the BBC website).

This either means the BBC have either stopped showing the banner, or have stored a cookie (without my explicit permission) to record the fact that the banner has been shown.

Anyway, I’m closing this issue now as the critics are not responding. I provided clear answers to the points they made and offered to debate with them.

Many people are finding this plugin useful because they find it to be simple and appropriate compared to the mostly over complicated and over the top solutions.

We wait to see how the law and its implementation will turn out in practice, and I will update users of this plugin as things develop.

So far everything has tended to re-affirm my approach (including the last minute update by the ICO to their cookie guidance on “implicit permission”).

Please keep your comments and reports coming.

Mark

I’ve seen that effect with other themes and quite like it (though its a bit squashed on yours!)

No problem with you using the text I created – go ahead – but I recommend that you “noindex” the page to avoid any problems with your SEO (in case others do the same).

You can create your own link – a solution would be for me to allow the link to be disabled and to allow a page to be created for editing if people want it.

Mark

I couldn’t possibly comment!

Not an issue with EU Cookies Plugin anywayz.

Thanks for reporting back.

Mark

This looks like a problem with your installation rather than the plugin.

If you type https://locutorium.com/wp2010/somerubbish you should get the WordPress not found page, not the server page. Try visiting https://thewebalyst.com/somerubbish to see what I mean.

Mark

mckendric,

Thanks for the bug report.

That’s very odd because the plugin is supposed to handle the “not found” before WP! What version of WP is on the WP2011 theme site?

Thanks for the “Cookies for Google Analytics” suggestion. This wording will appear in 0.7

Mark

mckendrick,

Thanks for contributing to the debate – its nice to hear another pragmatic voice! Thought I was all alone ??

I agree we need to monitor and respond in an ongoing way.

I was hit by a big unmissable banner on the BBC news site this morning (right across the top of the page). Yet another variation. It will be interesting to see how high profile websites handle this, because they are most likely to be test cases.

Mark

David,

Thanks for your comment, but I think you saying the update “proves” anything is way too strong. As I say, I think it vindicates my approach. Further moves in that direction will also justify it.

I think your point assumes I was arguing this complies with the letter of ICO guidance, but I have never claimed that and you can read precisely what I do claim, what I recommend, and why I recommend it in my blog.

So I think that you and microbe have missed the point of my plugin – which I contend “helps compliance” and clearly is not broken.

The plugin does not guarantee compliance, no-one knows what will in the end be deemed compliant, and if you read the updated guidance it is neither clear nor in fact logical.

For example, they use the analogy of visiting a doctor to suggest that visiting alone would not be “implied consent” to the doctor recording personal information about you. Er hello! Has anyone ever been to the doctor and had them ask before they recorded anything? I certainly have not, so the example given seems to me to show only that they are confused themselves. Or in fact that the analogy they chose can be used to argue that simply visiting a website is a form of implied consent, at least to the degree to which users might expect cookies to be used.

But my approach is not about achieving compliance. It is about not sabotaging your website traffic (e.g. with pop-ups), and not getting caught in the net of cookie law enforcement (e.g. by not doing enough). So to say my plugin doesn’t comply is both untrue (only a court can determine that), and irrelevant (I don’t guarantee compliance – and by the way, can you show me *anyone* who does).

So what to do?

If you believe it is appropriate to put up pop-ups, or put the privacy link in a banner at the top of your page for every visitor, then by all means do it. I don’t believe this is wise at this point. I suggest that the very few who do take such extreme measures do so only with good reason. It is my opinion, as I have explained here and at more length in my blog, this is not appropriate for the majority of websites – and I walk this talk. Go to any of my websites and you will find me using the approach I recommend (and my own plugin).

If you or microbe recommend otherwise, are you following your own guidance? If so, I hope you will contribute to the debate by sharing links showing what you are doing, and also the impact on yours (or your client’s) website traffic. If there’s no impact, then maybe it is appropriate for more websites than I suggest, but for most I think the work required will be enough reason to avoid it if at all possible. Again, as I argue in my blog.

If you want to take the point up in more depth, I hope you’ll read my reasoning and comment on it there, as well as following up here.

See:
How To Comply With The EU Cookie Directive (from May 26th 2012)

Best,

Mark

Well, at the last moment the ICO has changed its stance. So it seems those of us wise enough to be pragmatic have been vindicated!

The introduction of implied consent:
“…shifts responsibility to the user rather than the website operator, and will come as a relief to thousands of website operators who have been struggling to comply with new EU directives “

This means that theWebalyst EU Cookies Plugin is not just a pragmatic and sensible approach, but should meet the letter of compliance as required by the ICO, for most websites.

Even those with functions such as shopping carts can now heave a sigh of relief because they are no longer required to obtain consent before saving every damn cookie to a user’s machine!

Here’s some background:
https://www.guardian.co.uk/technology/2012/may/26/cookies-law-changed-implied-consent

I would appreciate it if microbe would now correct his assertions, and acknowledge that this plugin a) is not broken and b) does help compliance, and for the majority of websites is probably all that is needed. You might also kindly re-consider your star rating!

Mark

Hi dartiss,

Thanks for your comment and for explaining your position.

The purpose of this plugin is to do what is in the best interest of website owners and visitors. My opinion is that we must try to avoid putting up popups, scarey messages or any other measures that would devastate website traffic or break functionality. I believe such measures be against the interests of website visitors as well as owners.

I have investigated the letter of the law here, and followed the developments and debate amongst designers and enforcement, and am very aware of the information you cited. When I first looked into this I thought as you did! But let’s be realistic and think about how this is going to play out, and whether it is wise to be one of what I imagine will be a tiny minority of websites that follow the line you advocate.

No, as I point out in my reasoning (here: How To Get Ready For The EU Cookie Directive), I suggest that it is better for businesses and other website owners to take a decision about how far to go, and keep a close eye on how both practice and enforement play out. Again, I think this is also in the interests of users.

It takes no more than a moment to see that overly zealous enforcement (or implementation) will be unhelpful for users. So my approach, and my plugin, is designed to act in good faith, and genuinely seek to meet the aims of the law – which is to ensure users have the information and control (informed consent) necessary to decide what and how they and the personal information are treated when they visit a website.

I suggest you take a look at the post I mentioned for more information, and then let’s see what happens in practice.

I think it is unjustified to mark this plugin as broken and give it a zero star rating (as microbe appears to have done), when it does exactly what it says. I hope that microbe will review and reconsider in the light of what I have said. Or if not, to revisit those decisions when he sees what happens in practice.

I don’t expect masses of UK websites, let alone those world-wide, to suddenly be covered in Cookie Consent request messages on May 26th. Nor at any time in the future.

Time will tell!

Mark