• Resolved Graffic

    (@jubbas)


    Hi
    
    I am getting these errors in the console, and when I disable the site kit plugin the errors go away.
    When activated, I also get errors in the front end, where elements are missing and spaces between certain elements become larger.
    
    No warnings or errors in Site Health, and Site Kit dashboard looks normal.
    
    Using Version 1.127.0, and everything is updated on the site.
    I have disabled the plugin until I find a solution.
    
    Uncaught RangeError: Maximum call stack size exceeded
    at Array.concat ()
    at document.createElement (script.js:1:93043)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    
    Uncaught RangeError: Maximum call stack size exceeded
    at document.createElement (script.js:1:92906)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    
    Uncaught RangeError: Maximum call stack size exceeded
    at Array.concat ()
    at document.createElement (script.js:1:93043)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    at document.createElement (script.js:1:93024)
    
    TypeError: Cannot read properties of undefined (reading 'activeLaw')
    at O (banner.js:1:72221)
    at T (banner.js:1:74280)
    at banner.js:1:94322
    at f (banner.js:1:61063)
    at Generator._invoke (banner.js:1:60851)
    at Generator.next (banner.js:1:61492)
    at o (banner.js:1:68009)
    at a (banner.js:1:68212)
    
    Third-party cookie will be blocked. Learn more in the Issues tab.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Thanks for reaching out @jubbas. I’d be happy to investigate this with you. In order to do so, please share the following:

    1. Your Site Health information. You can use this form to share privately if preferred.??
    2. Is this a first time occurrence? If so can you share whether you installed any additional plugins recently?

    Let me know if you have any questions with the above.

    Thread Starter Graffic

    (@jubbas)

    Thanks James

    The Site Health information is now shared.

    We have not installed any new plugins in the past six months.
    Site Kit has been installed for a year now, and we found out that there was a error, when the site looked a bit wrong.

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for sharing @jubbas. From reviewing the details you kindly shared I don’t see anything that stands out. Do these errors appear on the Site Kit dashboard at any stage, or do they only appear as as browser console errors?

    I also get errors in the front end, where elements are missing and spaces between certain elements become larger.

    If you can share a video recording of this I can check this further with the team. You can use a service such as Loom or RecordIt to share a screen recording, while using the same form previously used to share this privately.?

    Within the screen recording please have your developer tools option within a Chrome browser incognito window. This can help rule out browser related caching impacting these errors.

    Let me know if you have any questions with the above. Thank you!

    Thread Starter Graffic

    (@jubbas)

    Did some further investigation.

    No errors on Site Kit dashboard at any stage, only in console and some parts missing or looking strange in frontend.

    We think the problems started when we implemented Consent mode v2., so we tried pausing it, but unfortunately it had no effect, even after a cache reset.

    We thought it HAD something to do with cokkies, so we disabled the CookieYes plugin.
    The strange thing is that with the CookieYes plugin disabled, the page works fine with Site Kit enabled with no errors in console.

    The error only appears in Chrome and Safari, in Edge and Firefox it looks fine.
    In Edge i get this in console though:
    Failed to load resource:
    https://www.googletagmanager.com/gtm.js?id=GTM-KCJ939J:1
    net::ERR_BLOCKED_BY_CLIENT

    Failed to load resource:
    https://snap.licdn.com/li.lms-analytics/insight.min.js
    Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

    Plugin Support James Osborne

    (@jamesosborne)

    Appreciate the update @jubbas.

    The strange thing is that with the CookieYes plugin?disabled, the page works fine with Site Kit?enabled?with no errors in console.

    You may wish to check does the same occur with the default settings of CookieYes, as I suspect it may be possible to encounter some errors although particularly on the front end of your site, such as if you don’t grant consent (as the Google tags may be blocked or non functional).

    The error only appears in Chrome and Safari, in Edge and Firefox it looks fine.
    In Edge i get this in console though:
    Failed to load resource:
    https://www.googletagmanager.com/gtm.js?id=GTM-KCJ939J:1
    net::ERR_BLOCKED_BY_CLIENT

    I suspect these may be related to your Edge browser and a possible extension or feature, such as an Ad Blocking.

    I’ll let you know after I confirm no conflicts with the default settings with CookieYes. You may wish to revert to the default settings also and check for any errors from the main Site Kit dashboard, in particular from a Chrome browser incognito window once more. Should not issues occur, I suspect you can disregard any errors when checking from another browser if your Site Kit dashboard is working as expected.

    Let me know if you have any questions with the above.

    Plugin Support James Osborne

    (@jamesosborne)

    Just to keep you updated on this, I’ve been testing CookieYes with Site Kit and in my case I don’t encounter the same browser console errors as per your site. That’s certainly not to state that there is no issue, it just make take some more effort to consistently reproduce. If you’d like us to check this further I’d certainly be happy to do so. If you can share a video recording of this I can also check this further with the team. You can use a service such as?Loom?or?RecordIt?to share a screen recording, while using the?same form previously used?to share this privately.?

    Within the recording please demonstrator the errors that appear on the browser console, while scanning through your CookieYes configuration. Thank you!

    Plugin Support James Osborne

    (@jamesosborne)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Console errors’ is closed to new replies.