|
|
Interesting. I like that. We could code Composr up to actually be able to tell the user what each cookie is, and perhaps put a "block" button next to each (not just delete) in some cases, or open the console in an overlay in other cases where a cookie has been auto-created. |
|
|
|
Sounds even better, with the overlay option and cookie info. |
|
|
|
Coming back to this and wondering why there isn't some kind of basic cookie acceptance overlay already given the laws. Do they only apply to certain cookies, or all cookies in general? Most sites have an annoying message announcing the use of cookies. Maybe if people tick those cookie options that may be illegal, it could trigger the message to show, if it's not that case that all cookies are liable in which case it should be shown anyway. Hmm. |
|
|
|
http://compo.sr/site/news/view/eu-cookie-legislation.htm |
|
|
|
Certainly a better way of doing it, and having seen those prompts I have no idea why I even asked about this. |
|
|
|
Adsense users are now being told they have to have a cookie control system in the EU. So we may need to have some system pre-integrated with Composr, turned on via a config option, for managing such third-party cookies. |
|
|
|
I've done a straight-forward integration of the Silktide Cookie Consent tool for v10. It is nicely integrated out of the box and behind a config option (defaults to off).
I think a full management console isn't needed, and I don't think there's a lightweight free JS solution for that anyway. The Silktide consent tool has been configured to link to the default privacy page, which says how cookies are used and will now also say that in-built browser tools can be used to clear out cookies. |
|
|
|
Thank you, I think that's a nice compromise :) |
|
