• Louis

    (@louisgeis)


    Wow. After trying so many different cookie plugins, this one is genuinely perfect. Clean setup, clear options, and it just works. Bravo on the beautiful work.

    The only small feature that could be missing is the ability to disable the cookie banner for specific user roles, especially for admins. That would be really great.

    Otherwise, bravo — this is truly top.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author fabiodalez

    (@fabiodalez)

    Thanks for taking the time to write this, and I’m glad the plugin is working well for you.

    Disabling the banner per user role is something I’m considering, and I’ve opened an issue to track it. I’m not promising it for a particular release, because there are a few decisions underneath it that are easy to get wrong, and getting them wrong in a consent plugin is worse than not having the feature at all.

    The first one is what “no banner” should mean for that user. Inside the plugin the switch that hides the banner is the same one that turns off script blocking, so the obvious implementation would not just stop showing you the banner as an admin: it would load every third-party tracker on the page with no consent recorded anywhere. That is the opposite of what this plugin is for, and an administrator browsing the site is a data subject like anyone else. So any version worth shipping would hide the banner and keep blocking on, treating that visitor as having accepted only the necessary cookies.

    The second one is that a role is not a person. If you set it for administrators on a one-person site, you are making a decision about yourself, which is fine. If someone sets it for Editors on a site with five editors, the site owner is deciding on behalf of five other people who never saw the notice. I’d rather the default behaviour be safe in that case than convenient in the first one.

    The third is page caching. Showing different HTML to different visitors is exactly what breaks full-page caching, and the plugin has a Cache Compatibility Mode for sites where that matters. Most cache setups skip logged-in users, so in practice this is less of a problem than it sounds, but “most” is not “all”, and anything I added here would have to account for it rather than work by luck.

    None of this is difficult to build. It’s a few hours of code. It’s the semantics that need settling, and I’d rather settle them before deciding whether and how to add it.

    One thing that may help you meanwhile: if what you want is to stop seeing the banner while you work on the site, and you don’t mind that trackers load on those page views, the scanner already has a mode that does this for logged-in administrators. It is not a substitute for what you asked for and I’m not offering it as one, but it may cover the day-to-day annoyance.

    Thanks again for the report and for the kind words.

    Thread Starter Louis

    (@louisgeis)

    Thanks for the detailed answer, this is interesting ! I had not considered all these questions. Good luck with the rest, and again, great work. Have a nice day.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this review.