• Hi, firstly, thanks for this plugin – it is by far the best cookie law plugin i found.

    just a few requests:

    1) can you please support “assumed consent” – if the user goes to another page without declining cookies then they have given consent
    2) an option to NOT disable cookies until the user has explicitly opted out
    3) have four apis – a) delete cookies, b) turn on cookies, c) turn off cookies, d) just show the popup (you do provide this already with the filter/shortcode, but currently it already disables cookies.

    at the 11th hour the uk are now allowed to support assumed consent.

    i think the above 3 features would make the plugin as flexible as it would need to be. by the way, i am loving the stats page!

    https://www.ads-software.com/extend/plugins/cookillian/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Anonymous User 4048828

    (@anonymized-4048828)

    Hi! Thanks for the kudos!

    I just happened to read the Guardian’s article about the “Implied Consent” as well. I’ll definitely look into integrating your suggestions into the next version.

    Thread Starter dkirkland

    (@dkirkland)

    Thank you!

    Anonymous User 4048828

    (@anonymized-4048828)

    Hi!

    Version 1.1 has been released today. It supports “implied consent” (as an option under “Alert Settings”), where the visitor goes to any other page within the website after seeing the alert, it will opt the visitor in.

    There’s also an option that will allow you to remove the cookies after the visitor has opted out, rather than before, but keep in mind that this is not compliant according to the ICO (prior consent is required to setting any cookies, except those cookies that are required to operate the website).

    The API has also been changed, giving regular PHP functions instead of the filters (old filters still in place for backward compatibility). It introduces the option to see if a visitor has implied consent, delete cookies, opt the visitor in or out. There is no specific function for displaying the alert only, although with the introduction of removing cookies after a visitor opts out, this should still leave you with flexibility.

    All the PHP functions have Javascript equivalents (either as function or variable), which is more suitable for WordPress websites using caching plugins, such as WP Super Cache.

    Hope this was what you were looking for!

    Thread Starter dkirkland

    (@dkirkland)

    brilliant. well done !

    Thread Starter dkirkland

    (@dkirkland)

    Hi, couple more questions:

    1) when i enable implied consent, i notice that if the user moves to a new page without explicit opt-in, the footer javascript isn’t added.

    1a) can you add the js on implied consent
    1b) can you add the js if the “delete cookies after opt-out” is enabled. assuming it would then be removed on the next refresh if the user explicitly opts out*

    2) is there a function i can use to check if cookies are enabled? i did add a check to see if cookillian_opt_in was set to 1 but a recent change allowed the value to be 2, so it would b e great if I knew of a function I could check rather then rely on a cookie that may change?

    3) the resp=2 seems to be behaving differently now. it used to result in the alert showing again. Has this functionality changed? I’d like to allow the user to change their mind by clicking on something in the privacy policy and used to provide a link with resp=2 set but this no longer works.

    Thanks again,
    Dan

    Anonymous User 4048828

    (@anonymized-4048828)

    Hi!

    Only the <noscript> portion should be removed from the footer if the person has opted in (whether explicitly or through implied consent) or opted out.

    The remainder of the JavaScript (as a link in the <head> tag) should still be there, and you will be able to use JavaScript functions to check if the user opted in, out, cookies are blocked and if the user implied consent. The full details are explained in the Help tab on the Settings page, under the heading JavaScript.

    There’s also PHP equivalents to the JavaScript functions, though they cannot be relied upon if you’re using a WordPress caching plugin (as the page only gets processed by PHP when it needs to be cached).

    As for clearing the settings, it’s ?cookillian_resp=2 that needs to be added to the URL. This hasn’t changed from previous versions.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘[Plugin: Cookillian] assumed consent’ is closed to new replies.