Support » Plugin: GDPR Cookie Consent (CCPA Ready) » Quick thought re Accept/Reject buttons

  • Hi Mark,

    Thanks for ths very useful plugin!

    I see the recent update adds a Reject button as well as an Accept button.
    If you’re using the default settings, with the [cookie_button] shortcode in your message bar, installing the update will automatically cause both buttons to be displayed in your cookie banner. It would be easy for an admin to miss this if they’d accepted the banner in the past, and didn’t think to clear the cookie and check again after updating the plugin.

    Since the Reject button by default doesn’t actually disable all cookies, this would lead to a misleading banner (and maybe under GDPR, a “fake” Reject option would be even worse than a banner that didn’t provide a Reject option? Your guess is probably better than mine one this front ;))

    Maybe a better default would be to leave things as they were for the [cookie_button] shortcode, and require admins to explicitly switch on the new Reject button with a different shortcode?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author markwt

    (@markwt)

    Hi @kona,

    We are storing a cookie “viewed_cookie_policy” for each activity ( accept / reject ). If user accepts, the value will be “yes”. If the user rejects, the value will be “no”. According to that site owner can restrict their cookies. Also, Reject will delete all the cookies that are stored in non-necessary category by the admin

    Hi Mark,

    It’s great that you’re working on this, all of us in GDPR land really need it 🙂

    I’m doing some testing with Google Analytics cookies (pretty common use case, I’m guessing!) and what I’m finding is that even though I’ve set up cookie records for the GA cookies and specified them as non-necessary, they’re not getting deleted when I click “Reject”, and they are still being set on subsequent page-loads (even after I go in and manually delete them.) The “viewed_cookie_policy” cookie exists and is definitely set to “no”.

    Am I misunderstanding what you mean by “Reject will delete all the cookies that are stored in non-necessary category by the admin”?

    In terms of cookies created by JavaScript includes like the Google Analytics script, I think you can’t necessarily control the browser’s execution order – is it possible that cookies could still [sometimes] get set, despite the Reject preference, because the JavaScript that sets them runs *after* the plugin’s cookie clean-up code?

    Also I’ve just seen this in the GA documentation here

    When using the recommended JavaScript snippet, gtag.js and analytics.js set cookies on the highest level domain they can. For example, if your website address is blog.example.co.uk, analytics.js will set the cookie domain to .example.co.uk. Setting cookies on the highest level domain possible allows users to be tracked across subdomains without any extra configuration.

    so it might be a domain mismatching issue? (The GA cookies are on the domain .mysite.com even if the site is running as http://www.mysite.com).

    • This reply was modified 2 years, 6 months ago by Kona Macphee.
    Plugin Author markwt

    (@markwt)

    Hi @kona

    Introduced an option to enable/disable “Reject” button. Please download the zip from here and replace the existing one.

    According to the value of “viewed_cookie_policy”, you have to put some code to restrict the cookie in your site.

    Thanks for the download, much appreciated!

    So, just so I’m clear, “Reject” won’t actually delete any cookies at all (not even ones explicitly set up as non-essential), and the button is simply a way of capturing the visitor’s preferences?

    Introduced an option to enable/disable “Reject” button. Please download the zip from here and replace the existing one.

    My thanks for this as well, I’ll be disabling the “Reject” button to avoid confusion from those who think clicking it will remove cookies automatically.

    Will this option also be in the next version? I take it from the URL you gave that it has now replaced the previous 1.5.4 on WordPress’s servers?

    I ask because I’m using it on multiple sites where I don’t want the “Reject” button for now.

    Many thanks

    • This reply was modified 2 years, 6 months ago by robf.

    Would you consider pushing this update as a new version 1.5.5? Otherwise a lot of folk who’ve already updated will miss the change (and WordPress doesn’t make it easy to re-install the same version of a plugin without fully deleting it and thus losing the settings.) It’s a significant change so I’d say it deserves a new point release!

    I’m using “Easy Theme and Plugin Upgrades” plugin which gets round the reinstall problem and keeps settings, but I agree that new version 1.5.5 would be preferable

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Quick thought re Accept/Reject buttons’ is closed to new replies.