Skip to main content

Cookiebot blocks every script on website

Comments

44 comments

  • Official comment
    Brian Mørkeberg Lundkvist

    Dear all

    Thank you for your input and feedback.

    We are looking into this as a matter of priority.

    We will report back here as soon as we have news to share.

     

    UPDATE 2020-03-27 7pm CET - 
    We have now managed to identify and hotfix a recently introduced bug causing issues with some event handlers not consistently firing when using Cookiebot in auto blocking mode. The result of this was some javascripts not loading on client websites on first visits to the website and some events on client sites not being triggered.

    We are very sorry for the inconvenience caused by this error and will look into taking further measures to secure early discovery of bugs of this nature to prevent a similar issue from happening in the future.

  • Daniel Lundahl

    Hello! I think this issue is back since it is blocking my local script to run, even though it doesn't create any cookies. 

    3
  • Paul

    We have the same issue. In auto mode, scripts are blocked even if they do not set cookies.

    3
  • Adam Jory

    Has this issue resurfaced? It's affecting our site. If the user selects only strictly necessary cookies, many parts of the site are just not shown. This wasn't an issue went we went live with the site earlier this year. Just under half of our users select this option and the impact has been noticed by the business. Please can someone look into this urgently.

    3
  • Henrik Bayer Nielsen

    This is also still happening for us.

    We have 20 websites running Cookiebot in auto blocking mode that periodically experience this issue.

    It's a MAJOR issue, making sites completely unusuable in some cases and absolutely not something that we can rely on.

    It seems random if Cookiebot decides to block for window.addEventListener('load', ...) and document.addEventListener('DOMContentLoaded', ...) except in Internet Explorer where it doesn't work at all........

     

    It's one thing if your product doesn't work. But the fact that you actually break websites with your updates is unacceptable. Who's going to pay for that downtime? Do we need to implement javascript uptime monitors or when do you plan to get this fixed?

    2
  • Begoña Alvarez de la Cruz

    Is it possible that this issue is back? We use svelte/sapper and I just realized that cookiebot is blocking the entire svelte/sapper client build, because it is marking the script as "statistics" for some reason:

    <script src="/client/foo-bar-ID/main.js" type="text/plain" data-cookieconsent="statistics"></script>. 

    How can I solve this? I cannot edit the way the framework injects the client main.js, so I need a way to prevent cookiebot from marking this as statistics.

    Please help, this is VERY important as the entire website is totally broken (it simply doesnt load) because of this issue for every single newcomer. 

    2
  • Sub

    We discovered the same problem today on a major site. Exactly same issue as described above.

    We need this fixed asap.

     

    2
  • Desirée Noack

    Hi,

    I have the same problem here.

    1. The Cookiebot script is included at the very top within the HEAD-tag.
    2. The scripts, which are blocked, do not set any cookies. For example the jQuery lib (jquery-3.4.1.min.js) is blocked and some other custom scripts, which definetly do not set any cookies.
    3. Except for the jQuery lib all other scripts are implemented in the footer.
    4. I tried the attribute data-cookieconsent="ignore" to exclude my custom scripts and the lib, but that didn't work. The MIME stayed text/javascript but the script was not executed anyway.
    5. If I use the manual blocking mode and add for example type="text/plain" data-cookieconsent="statistics" to those scripts, which set cookies, all works fine. My scripts do not get blocked except for those, which are marked appropriate. If the website user allows for example statistics, those scripts marked as described work fine too.


    To sum up: The data-blockingmode="auto" does not do the job and it is not reasonable to switch to the manual mode because we are a reseller and have many costumers. This would mean a lot of work to do.

    May there be an other solution?

    Regards,
    Desi

    Additional fun fact: I did not figure out what the real trigger is, but yesterday on some of our websites the scripts did not get blocked during the first page load (cache disabled the whole time in the developer tools). After clicking on another side, the scripts were blocked. Trying to reload did not fix the problem. Funnily enough the scripts got executed again after a few tries. And on other websites the scripts are blocked the whole time. That happend especially today.

    1
  • Mediacoding

    Dear CookieBot Support

    We have the same issues with the websites using your product.

    We created a special page to do some testing and found that the "DOMContentLoaded" and similar events are not fired when CookieBot is active.

    Our code (at the bottom of the page) can be found on pastebin: https://pastebin.com/mxRC6VYj

    "window.onload" does fire, but the other 2 (window.addEventListener('load', ...) and document.addEventListener('DOMContentLoaded', ...)) do not.
    The "readystatechange" event does not fire too.
    The timeout is triggered and the click-event works as well.

    I hope this helps you identify the issue.

    Regards,
    Patrick

    Edit:
    jQuery uses the one of those load-events to start, like:
    jQuery(document).on('load', function($) {
      // your code
    });

    1
  • Ralf Lambertz

    Dear team,

    Exactly same issue here for our customer's domain (www.albwerk.de). Since yesterday, scripts are blocked and page is not displayed correctly.

    Pls. urgently check and adivse!

    Thanks,

    Ralf

     

    1
  • KEMWEB

    Same problem here with many different pages.

    We needed to manually remove CookieBot from all domains to get them working again.

    All JavaScripts are blocked is CookieBot is not accepted.

    Fun fact: If I reload the page without cache it works. But normal page loads do not work.

    Please fix ASAP!

    1
  • KEMWEB

    We are still having this problem after rescan on multiple Domains.

    We will send a list to support...

    1
  • it

    We also run into the described problem.

     

    First thought was that our listeners behave weirdly due to re-initialization (uc.js loads our main javascript a second time (ticket 74150) ) but even when preventing that from happening the error still persist.

     

    Anyone found a workaround yet?

     

    1
  • Mel

    Happening on a number of sites for us too - media being blocked from loading in and animations not running.

    1
  • Hi Matthias,

    The above described problem might occur because the cookiebot script it not inserted as a first script into the head section. You should add the Cookiebot script at the very top within the HEAD-tag of your website. Please check the general implementation guide for more detailed information because this may be one of the reason why Cookiebot conflicts with other scripts: https://www.cookiebot.com/en/help/ 
    As you have mentioned that the script is inserted in first position of the header, please add the Cookiebot script into the head tag of your website. 

    However, the other reason why Cookiebot might blocks other scripts is that those scripts are setting cookies which are not classified and allowed by the visitors and therefore Cookiebot does not load them. If other scripts are setting cookies on the website you should classify those cookies and enable prior consent. 
    In case that those script are setting cookies and are needed for the site you could classify them as 'necessary'.
    Another solution which might works is to move/include the other scripts to the footer so they do not conflict with Cookiebot script which should be added into the head tag of your website.

    Could you please tell we if the other scripts work if your are using manual blocking mode. I am asking this because in case that other scripts are working after allowing cookies/manual mode this means that everything is working as it should. This is how Cookiebot works, it blocks/holds all elements which are setting cookies on the site until the user allow them. This is not a bug or a problem, this is how Cookiebot works and expected behavior regarding the GDPR requirements.  

    Regards,
    Spas

    0
  • Hi Desi,

    Considering the information and the issue you have described above it seems that the scripts are not really getting blocked. It's probably reference errors, cause by some scripts being handled by the auto blocker and some not. This from the other hand could causes some timing issues, where a script calls a method or variable that has not been defined yet.
    Could you please check your console for errors regarding some scripts or undefined methods or variables? 

    Regards,
    Spas

    0
  • Martin Szymanski

    URGENT

     

    Dear Cookiebot Team,

    we are recently facing the exact same issue using the auto-mode for our large customer base. The Cookiebot blocks the JS on our client websites and hence large parts of the websites are not being loaded.

     

    We are looking for a short term solution please - The issue is urgent for us.

     

    Best,

    Martin

    0
  • Desirée Noack

    Hi Spas,

    unfortunately, there are no console errors.

    Just to make that clear: The whole implementation worked for weeks for a whole bunch of customers. We noticed the issue yesterday for the first time.

    Regards,
    Desi

    0
  • Martin Szymanski

    We also noticed the urgent issue yesterday and it worked before (was reported by our clients).

     

    Best,

    Martin

    0
  • Neetu Dave

    URGENT

    Dear Cookiebot Team,

    Since yesterday at Enfield, we have been noticing the exact same issue(https://new.enfield.gov.uk/). We already have

    1. Cookiebot script at the very top of the page source-code, within the HEAD-tag.
    2. The cookie blocking mode is set to auto.
    3. 3rd party cookies, for the features that are getting blocked, is set as necessary. Eg. Live Chat
    4. The scripts, which are blocked, do not set any cookies. Eg. Jquery and Bootstrap

    Due to this several areas of the websites are not being loaded/functioning correctly. This issue is really urgent as this has now attracted a lot of Management and Leader attention.

    Please advise.

    Thanks,

    Neetu

    0
  • Benjamin Krause

    Same problems on sport-redler.de and danker-sport.de

     

    Fix it ASAP, pls

    0
  • KEMWEB

    We called CookieBot (+45 50 333 777) at 16 o clock (2,5 hours ago) and they did not know about the issue. Also they are not able to contact any engineer. That is only possible by mail. Could you believe this?

    Well, we did not get any mail response so far.

    Now it is 9 hours after first bug report and it still looks like no one is working on the issue.

    Not sure how many Euro we spend on CookieBot with all our customers but this is a no go.

    I am afraid we need to look at alternative solutions.

    0
  • Hahn

    Same here, my site doesn't show there pics anymore.

    0
  • Slapshot

    Hi Cookiebot-Team.

    we had the same problem suddenly popping up on wednesday afternoon CET.
    All of a sudden our site stopped working correctly for all users  that never accepted any cookies or just the necessary ones.

    This also happened on our production-environment, where nothing was touched for 2 weeks at that time.

    The page was just white, because the bundle- and chunk-files created by webpack containing our actual web-application where not loaded.
    Even if the user never consented to any cookies, the banner was shown, but the page was white. And if the user then accepted all cookies, the page remained white and only worked after a refresh.

    I already checked that these scripts does not set any cookies.
    At least, like I mentioned, this version of our application was deployed to production since 2 weeks and nothing was changed in the source-files of these scripts concerning cookies for about 2 months.

    All of the cookies found by the cookiebot-scanner can be located outside those blocked scripts and there haven't even been a new scan when the problem occured.

    So you see, a page which worked since at least 2 weeks without a problem stopped working suddenly without any change.

    For all of you, who are still struggling with this issue, I managed to "fix" this issue by setting data-cookieconsent="ignore" on the blocked script-tags.

    Beware that this solution should only be used in my opinion until cookiebot solves or clarifies this behaviour.

    Kind regards

    Benjamin

    0
  • Brian Mørkeberg Lundkvist

    Quick update:
    Could anyone still experiencing this please forward their domains to us at support@cookiebot.com - Currently we are no longer able to recreate the issues described.
    Please also, if this is still affecting your website, we encourage you all to please do a rescan of your domains to update your cookie blocking configuration. We expect that this will alleviate the issue.

    0
  • Linette Lynggaard

    Hello

    I am using Cookiebot plugin on all my clients wordpress websites. I have now 4 websites, where suddenly something does not work, on one website images and Heading tags disappears, another the menu is disappeard.  I have disabled cookiebot on all 4 websites, and now they work fine. 

    So it looks like there is a problem in general with cookiebot right now. 

    Can you please have a look at it - its a bit critical.  

    Thanks, 

    LInette

    0
  • sanjeev thapa

    Hello,

    I am also having severe issues on my production system.

    1. My wordpress site is messed up. Unfortunately, we cant disable Cookiebot.

    2. On my normal site, my javascript are not working, even a normal click events and general stuffs.

    This is very critical. Please help.

    0
  • Martin Szymanski

    Hello,

    the issue still remains and is not solved yet for us.

    I triggered a new scan of the cookies: Did not help.

     

    Will forward you the domain via mail

     

    Best,

    Martin

    0
  • Brian Mørkeberg Lundkvist

    Dear all

    The issue has now been identified and dealt with. Please see official response at the top of this thread for an update. Thank you for your feedback and patience on this issue. 

    Thanks.

     

    0
  • KEMWEB

    Thank you for the update.

    I can confirm the issue is solved.

    Thanks a lot!

    While you are looking for a better monitoring. The bug report was right here. Bug report per mail also. We even called. I think you mainly need to work on those communication channels.

    0

Please sign in to leave a comment.