Jump to content
adrian

Cookie Management Banner

Recommended Posts

Hi everyone,

Sorry for the silence on this thread. This module is now generously being managed and updated by @wbmnfktr - I have updated the modules directory entry to point to his fork. I am sure he will be able to better support and improve this module than I can.

 

  • Like 6

Share this post


Link to post
Share on other sites

@adrian Just a thought, could you go into GH and update your readme to point to the new code under @wbmnfktr's account and also your GH repo to "Archived"?

Many thanks for the work you've put into this BTW.

  • Like 4

Share this post


Link to post
Share on other sites

First of all... thank you @adrian for the introduction and the great work with this module.

In the last couple of days I created a DEV branch with some minor changes and fixes I found while testing the latest version (0.4.11).
If you are interested in playing around with that version, grab a copy over at Github - the DEV branch is linked below. As always: backup your site and previous module first.

All changes so far:

  • FIXED: Vanilla JS version notice toggle didn't work when MANAGE disabled
  • FIXED: Version change didn't trigger reset
  • INFO: Added usage examples (assets/html)
  • CHANGED: Removed CLOSE option
  • ADDED: Datalayer details to README

Issue tracking on Github was also enabled. This could make things easier in the future. Feel free to open an issue there whenever you find a bug. Don't forget to add the obvious details (ProcessWire version, PHP version, expected behaviour, your module settings and custom code).

DEV-Branch
https://github.com/webmanufaktur/CookieManagementBanner/tree/dev

Issues
https://github.com/webmanufaktur/CookieManagementBanner/issues

  • Like 9

Share this post


Link to post
Share on other sites

For those having access to the premium area of erecht24, here is an intersting information update after the last EUGH decisons:
https://www.e-recht24.de/mitglieder/updates/eugh-urteile-cookies-einwilligung-google-analytics/
The world gets more complicated every day and I think the cookie managers too.

Small comments:

  • Clicking "accept" was an agreement - so when opening the popup again later, the agreed checkbox could be pre-sected? Or better not?
  • I tried revoking rights, but the Google "GA" cookie is still present. Is deactivating the script enough, musn't there also the Google Tag Manager cookie removed?A
  • lso I can save "no" decision (no checkbox selected). I wonder what that means for the decision taken...

I compared this with a WordPress cookie manager and found 2 nice ideas:

  • There a simple counter of how many people opt out.
  • There are 2 links in the pop up under the "Accept" buttons in the right corner: Impressum and Privacy. So in case those madatory links get covered by the popup, those page are still easily accessible.


 

Share this post


Link to post
Share on other sites

Thank you @ceberlin for the link. I just looked into the article and will take a look at the tools they provide and how they work - hopefully this week.

12 hours ago, ceberlin said:

There are 2 links in the pop up under the "Accept" buttons in the right corner: Impressum and Privacy. So in case those madatory links get covered by the popup, those page are still easily accessible.

Those can easily be set in the texts you already show in the banner. That's how I do it most of the time.

  • Like 1

Share this post


Link to post
Share on other sites
2 minutes ago, wbmnfktr said:

Those can easily be set in the texts you already show in the banner. That's how I do it most of the time.

I do, too. But I thought having the links placed UNDER the Confirm buttons makes more sense? And using a PW selector for the pages takes besser care that the links do not break on changes. (Text links are easily overlooked ?)

Share this post


Link to post
Share on other sites

Hi,

is it possible to display the notice as an overlay. I've only the possibility to choose "Fixed Overlay at Bottom of Page"

633913644_2019-11-2610_35_33.jpg.3255d8105ff0b1a8431f0be3ff10c706.jpg

I'm using Version 0.4.12 (dev branch) from @wbmnfktr github repo.

Furthermore it would be really nice to have the ability to create more than one checkbox in order to allow users to pick cookies more specifily. See https://developers.deezer.com/ for an example.

Many greets!

Edited by DV-JF
Added screenshot & branch info

Share this post


Link to post
Share on other sites
1 hour ago, DV-JF said:

is it possible to display the notice as an overlay. I've only the possibility to choose "Fixed Overlay at Bottom of Page"

I could add a second option to that dropdown. Something like CustomCSS, add a specific class to the HTML and you can add your very own CSS and style it however you like it.

Another way would be disabling the auto-load assets option in the settings and add custom CSS right away.

1 hour ago, DV-JF said:

Furthermore it would be really nice to have the ability to create more than one checkbox in order to allow users to pick cookies more specifily.

I thought about something like that but I'm not sure which way to go here - for now.
The solution used by Deezer is provided by CookieBot and is quite powerful. Yet a bit too much for most I guess.

What/which options do you need in most of your projects?

I'm happy to hear more opinions, suggestions and ideas.

  • Like 2

Share this post


Link to post
Share on other sites
5 minutes ago, wbmnfktr said:

I could add a second option to that dropdown. Something like CustomCSS, add a specific class to the HTML and you can add your very own CSS and style it however you like it.

I'm just wonderin because of last point from READE.me say:

Quote
  • position selection (top or bottom overlay, or content pushed down from the top)

So I'thought this is already implemented.

7 minutes ago, wbmnfktr said:

Another way would be disabling the auto-load assets option in the settings and add custom CSS right away.

I know, just wanted to save some time 😁

8 minutes ago, wbmnfktr said:

I thought about something like that but I'm not sure which way to go here - for now.
The solution used by Deezer is provided by CookieBot and is quite powerful. Yet a bit too much for most I guess.

What/which options do you need in most of your projects?

I think it would be great to be relative flexible. Perhaps we may have a field (maybe a repeater could do) where you specify what kind of cookies your website serves.

On each repeater there should be in my eyes some possibility to explain what the cookie does and why it is used.

I also like the "Necessary" checkbox which can't be disabled.

BTW: Great module, thanks for @adrian creating and @wbmnfktr for maintaining it!

  • Like 2

Share this post


Link to post
Share on other sites

As some of our customers do have the same request (checkbox for only necessary cookies), I implemented this option in this fork.
Till now I only added the option in the vanilla js solution as we don't use jQuery at all. If desired I could add also this option to the jQuery part and open a PR.
Technically the button for "only necessary" cookies is the same as the option to not consent at all, just a different position of the button and naming.

328158894_Bildschirmfoto2019-12-03um11_47_46.thumb.png.72c79d981c586aadcf4a88409c2c5379.png

This is an example of the module frontend.

  • Thanks 1

Share this post


Link to post
Share on other sites
1 hour ago, joshua said:

Technically the button for "only necessary" cookies is the same as the option to not consent at all, just a different position of the button and naming.

On first look this sounds like a really nice and handy addition and workaround for several use cases that were already mentioned here.
I have to take a closer look how this works out in the backend and frontend of course but I guess I'll be happy to add this to the module - somehow.

But as you use cookieMonster.block() for your necessary cookies the stored information (localStorage) says cookies denied/blocked and there might be a difference in these so it might be better to store a different value than blocked.

 

  • Like 1

Share this post


Link to post
Share on other sites

I agree that there should be a different value for necessary cookies...
Maybe the pwcmbAllowCookies in localStorage could have values like "all", "necessary" and "no" instead of just "y" and "n"?

I also thought about respecting the "DoNotTrack" choice of the user in the browser. I'm currently working on this, but this simple snippet at the start of the init function should do it:

/*
 if the user activated the "DoNotTrack" function in their browser, respect that choice and do not show the banner
 */
if (navigator.doNotTrack) {
  cookieMonster.cfg.allowCookies = "n";
  cookieMonster.cfg.selectionMade = "y";
  cookieMonster.cfg.storedVersion = cookieMonster.cfg.version;
  cookieMonster.sendActionBeacon();
  cookieMonster.updateStatus();
  cookieMonster.sendTrackingBeacon();
  return;
}
  • Like 1

Share this post


Link to post
Share on other sites
8 minutes ago, joshua said:

values like "all", "necessary" and "no" instead of just "y" and "n"

That's exactly what I thought about. As it's a change with bigger impact it might break already existing installations/setups. Therefore this has to be announced very well in that upcoming release - whenever it will happen.

While DNT is kind of great and standard I had issues with it in the past - quite some time ago - but I actually love the idea. As it would support Privacy by default it might be something not everyone (site owners, marketers, ...) wants, so it could be another option in the settings.

I really appreciate your input and ideas!

Share this post


Link to post
Share on other sites

It's a pleasure 🙂

Yes, DNT should also be a selectable option. I'll add an suggestion for this feature later.
 

4 minutes ago, wbmnfktr said:

As it's a change with bigger impact it might break already existing installations/setups. Therefore this has to be announced very well in that upcoming release - whenever it will happen.

That's true. To add this as a non-breaking feature we could also add the type of accepted cookies as a separate storage option "allowedCookieType" => "all" // "necessary". In this case no existing setup should break.

  • Like 1

Share this post


Link to post
Share on other sites

That could do the trick.

Yet another thing comes to my mind. It needs to be somehow managable for users to see what decision they made.

How do you handle that in your fork/version? I didn't see anything in your code that tells users their "only necessary cookies" decision.
Maybe it's there but I haven't installed your version yet.

Share this post


Link to post
Share on other sites

You're right, this isn't included yet. I definetely need to update the code later 😉
 

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...