I've just visited the demo site, which has put a cookie on my computer without me clicking the "I'm happy" button - the new regulations state that users have to give consent before cookies are put on their computers. Also, with Javascript turned off there is no action.

I don't think this module does what you want it to.

Comments

matt b’s picture

Verified - I was issued with 2 cookies without my consent. I'd prefer a solution that did not rely on a third party.

budda’s picture

Status: Active » Closed (works as designed)

I cannot comment on the civicuk.com site used for the demo but this module still requires rouge Drupal modules or javascript widgets to be wrapped in callback functions which are only called if the user has agreed to accept cookies.

This module is self contained code hosted on your server, and no 3rd party service is being accessed from your site.

matt b’s picture

Thanks budda

Do you have a demo site of the drupal module in action?

Mark Steven’s picture

Matt, those are load balancer cookies. These are an essential aspect of CIVIC's server infrastructure and as such explicit consent is not required before you drop these cookies.

matt b’s picture

Shows just how confusingly stupid the whole thing is then doesn't it! (But thanks for the module!!)

Adam Wood’s picture

First, thanks for the module. It a great solution for Drupal users effected by this policy.

Regarding this module being 'self-contained'...

Whilst this modules' code is self-contained, upon trying to theme the module, it's obviously that it's loading its image from Civic UK's server, so I don't know how it can be described as 'self-contained'.

This isn't a huge problem, it just involves overwriting this in the CSS. However, why, when you have an images folder for the module, aren't the images just loaded from there?

Examples;

background-image:url(http://www.civicuk.com/cookie-law/images/ccc-icons.gif)
background-image:url(http://www.civicuk.com/cookie-law/images/widget-x.gif)

In addition, it seems to just make theming the module (i.e. editing those images), much harder...

budda’s picture

Regarding this module being 'self-contained' - it was in response to the use of the javascript.

Can you elaborate how themeing the pop-up is difficult and suggest improvements to the module code that might help?

Adam Wood’s picture

Hi budda,

Apologies, I was talking about it on a more general basis.

It just seems strange to include certain images with the module, and host some on Civic's server... By calling the images from civicuk.com, it adds unnecessary dependancy and loading time.

In regards to theming it. I was referring to theming the images; ccc-icons.gif and widget-x.gif. Instead of just being able to edit the images in the module, I had to grab the images from the civic url, edit them, upload the into the module and point the css over to the locally stored images. As opposed to just editing the image and re-uploading it.

I would submit a suggested patch, but there isn't any point as it requires the images in the module.

If it would be of interest, I'd be happy to look at/help with a patch to allow users to change the theming (color scheme) of the buttons/widget/popup from within the module settings?