marksteven1

Hi Gozalbes,

Geolocation is not enabled on the free version at all. I’ll take a look and see if there’s anything we can do to make this clearer.

The product requires registration. This enables us to maintain product licenses and also maintain a single code-base.

We will review product descriptions on the WordPress site in order to make what the free and paid for versions of the product do a bit clearer.

Feel free to take a look in a little while and let me know if there’s anything else we can help with.

Mark

Mark Steven
[sig moderated as per the Forum Rules]

Hey Mr_Cynical,

Sorry you feel that way!

The paid version enables some nice additional features like geo-location, a top bar and bottom bar interface, support for sub-domains and permission to rebrand the plugin.

The free version continues to be, well, free, and easily configurable via the module.

Yes, Cookie Control requires registration in order to generate the API key and this enables us to manage licenses properly.

CIVIC does not use server request data for other purposes or store it in any identifiable format.

I think there’s an underlying point which is quite valid around how we describe the module on the WordPress site, and we’re updating that to be a bit more explicit about what’s in the free and paid-for versions of the product.

Mark

Mark Steven
[sig moderated as per the Forum Rules]

Hi Mieneke,

Cookie Control provides a set of functions and call backs which you need to use in order to “catch” cookies set by other scripts. This is as it should be. To automatically “catch” all cookies is impossible – what really happens is that you allow them to get set, and then globally delete cookies after the event, which isn’t that great. Later versions of Cookie Control (which haven’t made it to the WP plugin yet I’m afraid) support this method too, but from a technical point of view we see it as a fall-back rather than the right way of doing things…

In other words, you need to add some code to your JetPack scripts so they’re only setting cookies when the Cookie Control allow cookies cookie is set.

Examples of this kind of thing can be found here: https://www.civicuk.com/cookie-law/deployment.

Hope that helps

@hairyhobo… if you can be specific about what you’re trying to achieve, perhaps we can help you.

No worries – it’s perhaps something we should improve on if we get a chance…

Have you tried using the full country names in your list? E.g:

United Kingdom,Germany,Europe

In tests on Cookie Control this is what we’ve tended to use.

Hmm… peculiar. If you could provide a link to your site I’ll try and see what’s going on.

Try using country codes to INCLUDE countries where you want Cookie Control to appear: it’s not an exclude list.

We’ve agreed with the plugin developer that the link can be removed from the user interface (so @mentalist3d, no more 1000 links).

We would request users to include a link to the tool however, a suitable place being their privacy policy.

Hope that solution is acceptable to everyone.

Hi Ipstenu,

The link back to the Cookie Control pages is there for two reasons:

1) there’s information there to inform users what the tool is for.
2) we want to make the tool as widely available as possible – thus increasing user understanding and raising opt-in rates.

We’ve developed the tool in collaboration with government, and it is the recommended solution within the Scottish Government. If you’re in any doubt about the authenticity of the tool, this list of sites using it should set your mind at ease:

[ Thank you, we get it, the code is being used by government web sites. ]

CIVIC doesn’t stipulate many restrictions on using the tool, except that the link must be maintained and the iconography used – there are good reasons for this.

And please bear in mind that while CIVIC is benefitting from publicity around this, we have worked hard to develop a solution and make it available freely, for the whole community to use.

Cheers,

Mark

Mark Steven
Head of Client Services, CIVIC