Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
According to GDPR rules if you change something in the cookie policy, users must review those changes and accept it again.
One solution could be to introduce a version field in the administration after the Privacy policy link and set a cookie with the accepted version. This way we can check if there is a newer version of the Privacy policy.
If anyone done this so far please upload the solution. (If not, I will try to implement this in the future)
Comments
Comment #2
svenryen CreditAttribution: svenryen at Ramsalt Lab commentedIf you need to ask consent again, you can change the name of the cookie (under advanced). This will result in all users seeing the banner again.
Comment #3
svenryen CreditAttribution: svenryen at Ramsalt Lab commentedComment #4
L_VanDamme CreditAttribution: L_VanDamme at Dropsolid commentedReopening this ticket as I agree with the initial request.
Changing the cookie name will not always be an optimal solution as this might require reconfiguring third parties like Google Tag Manager.
Comment #5
L_VanDamme CreditAttribution: L_VanDamme at Dropsolid commentedComment #6
svenryen CreditAttribution: svenryen at Ramsalt Lab commentedThis could indeed be something worth looking into. I'm bumping priority to Major.
Comment #7
Grayle CreditAttribution: Grayle at Dropsolid commentedD7 patch. Based on version. Admins can change the version to reshow the popup.
Won't trigger a reshow when updating to this version, so as not to needlessly show the popup.
Going to start on the D8 patch now.
Comment #8
Grayle CreditAttribution: Grayle at Dropsolid commentedD8 patch
Comment #9
Grayle CreditAttribution: Grayle at Dropsolid commentedUpdated D7 patch to make version field required, to match D8 patch.
Comment #10
svenryen CreditAttribution: svenryen at Ramsalt Lab commentedHere's some feedback. Applies to both D7 and D8:
Looks good. Here's some feedback. I haven't applied the patch, will do that once these items have been resolved.
Why is version 0.0.1 by default? Wouldn't it make more sense if it was 1.0.0? And I think we should label the new value 'cookie_policy_version'
Do we want the cookie name to reflect the base name that the module uses?
This title uses abbreviation, could that confuse some users? It would be better to spell the name out fully. Though here we don't need to repeat EUCC, I suggest using "Privacy policy version" since it better reflects the nature of this setting.
I feel we need a native Englishman to help us with a short and concise sentence. The best I can come up with is "Change this value to make the cookie information banner reappear for all visitors. A typical usage of this field is to increase the value when the privacy policy has been changed."
Check the version number here as well.
cookie_policy_version would be a better name.
Comment #11
Grayle CreditAttribution: Grayle at Dropsolid commentedUpdated D8 patch
Comment #12
Grayle CreditAttribution: Grayle at Dropsolid commentedForgot to replace an instance of the old 'version' field in the javascript file.
Comment #13
Grayle CreditAttribution: Grayle at Dropsolid commentedJesus. This is why you don't work on an empty stomach.
Comment #14
Grayle CreditAttribution: Grayle at Dropsolid commentedComment #15
Grayle CreditAttribution: Grayle at Dropsolid commentedComment #17
svenryen CreditAttribution: svenryen at Ramsalt Lab commentedComment #20
svenryen CreditAttribution: svenryen at Ramsalt Lab commentedThanks for the contribution!