Closed (fixed)
Project:
EU Cookie Compliance (GDPR Compliance)
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Jul 2019 at 12:45 UTC
Updated:
10 Sep 2020 at 19:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
saschahannes commentedI have the same problem.
Comment #3
finabluma commentedsame here :(
Comment #4
svenryen commentedCan you run
drush cget eu_cookie_compliance.settingsand paste the output here?Comment #5
saschahannes commentedComment #6
svenryen commentedThanks. I'll have a look tomorrow.
Comment #7
saschahannes commentedOkay, thank you for your quick response!
Comment #8
svenryen commentedHi! I imported the config on 1.8, but can't reproduce. When I click "Ok, ich bin einverstanden", the banner disappears and I do not see any message in the console. Which browser are you using? I've tried Chrome, Firefox, Safari and even IE 11.
Comment #9
lobodakyrylo commentedI had the same issue. I used minifyjs module on my website and I minified eu_cookie_compliance.js so the website had the old version of the file.
I just re-minified eu_cookie_compliance.js file on the performance page and cleared cache and it started working.
Comment #10
heikkiy commentedThe actual problem seems to be that the eu_cookie_compliance.libraries.yml still lists all the library versions as 1.0. If you had a previous version of the module installed, it loads the previous versions from Drupal cache. It keeps trying to find the old version from the cache at /modules/contrib/eu_cookie_compliance/js/eu_cookie_compliance.js?v=1.
Problem is solved if you edit eu_cookie_compliance.libraries.yml from the module directory and change all version 1.0 numbers to for example to 1.1. Clear Drupal caches after this. It should now load all the library files from /modules/contrib/eu_cookie_compliance/js/eu_cookie_compliance.js?v=1.1 and you should get a fresh working version.
Comment #11
heikkiy commentedAttached is the problematic libraries file.
Comment #12
heikkiy commentedAttached is a patch which increases the libraries version number to match the module.
Comment #13
anybodyComment #14
anybodyPatch #12 is ok. I would have thought clearing caches would also fix that kind of problem but #12 definitely won't break anything...
Comment #15
neslee canil pinto+1, this looks like a fix.
Comment #16
svenryen commented@HeikkiY and @Anybody
Does this imply that we need to bump the library version number every time we release a new version with an updated js file?
Comment #17
svenryen commentedBumping the version numbers to 1.9 to match the current version.
Comment #19
svenryen commented