Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-open Banner when add new script #32

Closed
venumdev opened this issue Jun 25, 2018 · 9 comments
Closed

Re-open Banner when add new script #32

venumdev opened this issue Jun 25, 2018 · 9 comments

Comments

@venumdev
Copy link

Hi to all,
how do I re-open the banner to those who have already accepted the coockie previously once new scripts have been implemented?

@tobias-kuendig
Copy link
Member

Good question, @ayumihamsaki do you know what to do in this case? If a user adds new scripts via the backend should the banner reappear again?

@damsfx
Copy link
Contributor

damsfx commented Jun 25, 2018

@tobias-kuendig , according to Recital #32 :

Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject's agreement to the processing of personal data relating to him or her ....
Consent should cover all processing activities carried out for the same purpose or purposes. When the processing has multiple purposes, consent should be given for all of them .

With that say, I think if the list of scripts/cookies change, the banner has to be visible again in order to get the explicit consent for all services.

If you are more confortable with German language see : Official Journal of the European Union side by side EN/DE

@ghost
Copy link

ghost commented Jun 25, 2018

@venumdev Hi, I spoke about this in issue: #23

Your question would be under the "Show"

You have two choices:

  1. To re-open the banner.
  2. Or Link to the Advanced Settings Page. (e.g. in the footer)

I would recommend just adding a link in the footer saying:

<a href="https://www.example.com/privacy-and-cookie-policy">Update Consent</a>

Info about this can also be found inside the cookie plugin (I added it yesterday) found by navigating to:

OctoberCMS Back-End > Settings > GDPR and ePrivacy (Tab) > Info and Help > Information about GDPR and ePrivacy > Table of Contents (Section 23 - Show)

If however you are totally set on re-showing the Banner please comment below and we will add this feature.

(The reason for linking in the footer is to cover you legally for "Users being able to change their consent settings at any time". So that is why it would be best to only show the banner once after the user has clicked on dismiss, accept or reject).

I did write and explain all that and more in the info section. Check that out and it goes into more detail for you!

Anyway, let us know if I didn't answer your question? OR you are dead set on re-showing the banner.

how do I re-open the banner to those who have already accepted the coockie previously once new scripts have been implemented?

If a user adds new scripts via the backend should the banner reappear again?

No, banner should not show a second time if you add more scripts. It would be annoying to users! Just create a link in the footer to pass the law. Because the User would not edit the "New Scripts" in the Banner they would edit the "New Scripts" in the "Advanced Settings" Page. You do NOT need to re-show the Banner to Users again who have already given consent previously!

p.s. Will update the info section to answer that exactly as well. It's a good question!

@ghost
Copy link

ghost commented Jun 25, 2018

Cool updated the Plugin Info Section see Screenshot:

untitled

~Will do a Pull Request on it now.

@ghost ghost mentioned this issue Jun 25, 2018
@ghost
Copy link

ghost commented Jun 25, 2018

I just thought, you should also "date the policy" if you do any changes and maybe also archive them, I have done a second Pull Request to add that extra info as well, see screenshot:

untitled

@ghost
Copy link

ghost commented Jun 25, 2018

@tobias-kuendig What do you think about adding a feature to let webmaster's "archive" old config setups and be able to display them on the front end?

e.g.

Jan 2018 (Old - Archived)

  • Google Analytics
  • Facebook Pixel
  • Twitter Timeline

May 2018 (New - Current)

  • Google Analytics
  • Facebook Pixel
  • Twitter Timeline
  • Google+ Badge
  • CrazyEgg Analytics

Front-End

https://www.example.com/cookie-policy ← (New - Current)

{% component 'cookieBanner' %}

https://www.example.com/cookie-policy/jan-2018  ← (Old - Archived)

{% component 'cookieBanner' archive='1' %}

archive='0' = default/current

See: https://octobercms.com/docs/cms/components#component-variables

tobias-kuendig pushed a commit that referenced this issue Jun 26, 2018
This extra info is in regards to Issue: #32
@venumdev
Copy link
Author

It would not be better to generate a cookie that keeps track of the saved version. If the version is different, have the banner reopen?

@tobias-kuendig
Copy link
Member

I guess if it's not neccessary to show the banner a second time we really shouldn't do it since this is distracting to the user.

@tobias-kuendig
Copy link
Member

Since it is sufficient by the law and better UX we won't include an option to re-show the banner again if the cookies have changed. Make sure to place the settings link into your footer so users can update their consent at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants