I updated to version 7.x-1.24. Later also to 7.x-1.25 but the problem is always the same.
I played with different options, etc... but the message is always this one:
We use cookies on this website to enhance your user experience
You have given your consent for us to set cookies.
Look in the attached image...
1. If I select "Consent by default. Dont provide any option to opt out." I should not see the button "Withdraw consent" or at least it should be disactive.
2. I did not understand but from 24 to 25 version I played a lot and even of it was "enable banner" checked, I could not see it...in one moment I did not understand why it appeared....The cache I cleared 1 millions times, it was not from there...
3. In the message to the final version the message contains tags like < h2 > and < p > ... I updated them in the install file of the module. uninstalled and installed again the module, but the definition in the variable in the DB remained always the same...I removed these tags in the variable and it starts to show me errors...
Comments
Comment #2
svenryen commentedHi! Thanks for writing in. Can you please run `drush vget eu_cookie_compliance` and paste the output here?
Comment #3
svenryen commentedDoes your site use multiple languages?
Comment #4
tandim commentedComment #5
tandim commentedthank you very much for the fast answer.
no, my site use only one language.
I executed the command - the result is in the attachment result.txt
Comment #6
svenryen commentedWhat will resolve your situation is this:
1) Open the EU CC admin page
2) Select "Opt in" or "Opt out" consent method
3) Scroll down and uncheck a checkbox in front of "Enable floating privacy settings tab and withdraw consent banner"
4) Select "Consent by default" consent method
5) Save
Comment #7
tandim commentedComment #8
svenryen commentedComment #9
tandim commentedDone, but not visible anymore any pop-up message notification for cookies..... "we use cookies on this site to ......."
Comment #10
svenryen commentedHmm... I'm not sure I follow your last comment. Are you still having any issues with the module?
Comment #11
tandim commentedmy issue now is that I do not have any notification....since the ussues were in the notifications, if we do not have them we do not have anymore my previous issues, but I do not think it is the correct solution :)
If the settings of the module is "consent by default...don't provide any option to opt out" the web site should show anyway something like "hi guy, my web site use cookies and there is not options to choose...if you want to use the web site, we use cookies...."
Comment #12
svenryen commentedWhat's the value of the "cookie-agreed" cookie?
Comment #13
tandim commentedsorry, how to check it?
Comment #14
svenryen commentedWhich browser are you using?
Comment #15
tandim commentedchrome, IE, firefox...
Comment #16
tandim commentednow it is visible again (I did not understand from what it pushed to appear....I changed the options many times....)
The format of the message is as I reported in the beginning...
Why only one of the messages is visualized in a bad way.... with tags of < h2 >, < /h2 >, < p >, < /p >....(the first image attached) .
After I withdraw the concent, the other message is showed correctly (also it is formatted with the same tags < h2 >...) The first sentance is with bigger letters, the second in other line...etc..
Abou this "cookie-agreed" cookie...in any case, if I use the incognito browser it should not remember anything from the previous sessions, right?
Comment #17
svenryen commentedIn Chrome to inspect your cookies: https://developers.google.com/web/tools/chrome-devtools/manage-data/cookies
If your tags are being printed in the banner, you have a problem with the text filter format. Either you have selected "plain text" or you have errors in the configuration of the active text format.
Comment #18
norman.lolThe 7008 update hook sets
$eu_cookie_settings['withdraw_enabled'] = 1;while in the install hook it's set to'withdraw_enabled' => 0,. The update hook at least unwillingly enabled the withdraw banner for people who already had the module up and running and therefore had no method set. In a broader logic I think it's much better to also check if NO method is set at all OR method is set todefaultto prevent this from happening to all sites where this module was enabled before the latest feature-rich releases.Comment #19
norman.lolAnyways, I can confirm #6 for fixing this issue manually :)
Comment #20
besek commentedOption #6 worked for me. But this hould be fixed - those option should be hidden in configuration when it actually impacts site.
Comment #21
svenryen commentedI will work on a patch, but probably not before Sunday.
Comment #22
hotwebmatter commentedThe
'withdraw_consent'fieldset is currently hidden by the Drupal Form API#statessystem when the consent method is set to "Consent by default."Some may find it useful to prevent this fieldset from being hidden, so that they can easily enable/disable the floating "privacy settings" tab and "withdraw consent" banner even when the consent method is set to "Consent by default." This patch accomplishes that for 7.x-1.x.
It is also possible to access the hidden fieldset by the workaround in comment #6, but this workaround is not very intuitive.
Comment #23
hotwebmatter commentedHere's the same patch from the previous comment, uploaded again with a better filename (following drupal.org patch naming conventions.)
Comment #24
svenryen commentedThanks for the patch, though there's a different approach planned for the next version. We don't support that option for "Consent by default" (since it contradicts the consent method), so the setting will be stripped away in the submit handler if present.
Unfortunately, it's taking a bit longer to apply patches and tag a release in the summer months and I can't give a fixed date for the next release.
Comment #25
svenryen commentedComment #26
svenryen commentedThis attached patch resolves the issue.
When the Consent Method is "Consent by Default", we ensure that the "Withdraw tab" can't be shown by explicitly hiding it when the form is saved.
I hear some of the comments in the issue asking for a "Privacy settings" tab to be shown even when using "Consent by default". This is not something we currently offer, though you're welcome to open a new issue if you want to provide a patch. Just enabling the form field in all situations will lead to a misleading cookie acceptance interface, since you seemingly offer a method for revoking consent, even when you're actually not.
Patches are attached both for Drupal 7 and 8.