Skip to main content

SyntaxError: expected expression, got ')'



  • Official comment
    Richard van der Velde

    Hi Thanassis,

    Thank you for bringing this to our attention. We'll investigate and see if we can reproduce the error.

  • henry smith

    We had this same issue just now and traced it to one of the window.eval calls in cc.js. It looked like some of our config values had gotten "forgotten" somehow but they were still there in Saving a change in seems to have fixed the issue for us.

    Good luck 🙏

  • James Corkhill

    We had this same issue this morning on a clients wordpress site. Having resaved it in the banner is working.

    However it seems not to be displaying some content now if its not accepted.

  • Hugues Labaste

    I got the same issue.

    VM491:1 Uncaught SyntaxError: Unexpected token ')'
    at eval (<anonymous>)
    at CookieControl.Dialog.hide (cc.js?renew=false&referer=<<<MyWebSite>>>&dnt=false&forceshow=false&cbid=<<<MYID>>>&whitelabel=false&brandid=CookieConsent&framework=:1)
    at CookieControl.Dialog.submitConsent (cc.js?renew=false&referer=<<<MyWebSite>>>&dnt=false&forceshow=false&cbid=<<<MYID>>>&whitelabel=false&brandid=CookieConsent&framework=:1)
    at <anonymous>:1:18

    when we call :  Cookiebot.dialog.submitConsent()


  • Richard van der Velde

    Hi guys,

    I believe the issues you're experiencing are related to an attempt to factor out the use of the eval method in cc.js. Shortly after release we noticed this had an undesirable effect on those users that utilize a custom banner.

    We've rolled back the change and are attempting to find a solution.

    Those of you affected by this have probably a cached version that updated while the alternative solution was live. As some of you have already mentioned, making a small change and saving will renew the cache and resolve the issue.
    We're also preparing to flush the cache on our end for all domain groups using a custom banner, to ensure that only the newest updated version is cached.


Please sign in to leave a comment.