Errors from Blocksy (2.0.32) Cookie Consent extension

  • Resolved septero

    (@septero)


    8 months, 1 week ago

    After update to the latest Blocksy version I get below errors in the console log. Errors are related to Blocksy cookies consent extension. If I disable this extension all errors are gone. I didnt change anything on the website only updated the theme. How to fix it?

    WordPress: 6.4.3

    Blocksy Theme and Companion: 2.0.32

    Website: https://septero.pl

    Uncaught (in promise) TypeError: i is undefined

p https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

promise callbackp https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8 s https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8 EventListener.handleEvent https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

main.js:8:4893

p https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

(asynchroniczny: promise callback)

p https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

s https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

(asynchroniczny: EventListener.handleEvent)

https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

https://septero.pl/wp-content/plugins/blocksy-companion/framework/extensions/cookies-consent/static/bundle/main.js?ver=2.0.32:8

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

Viewing 6 replies - 1 through 6 (of 6 total)

  • Hello @septero

    Hmm, I do see that you have the litespeed plugin that’s processing JS files on your end, which might have an old cache as the latest versions of Blocksy have updated the core files.

    Can you please attempt to first temporarily disable the litespeed plugin as a whole to rule it out?

    Thanks!

    Thread Starter septero

    (@septero)

    Hi,

    Thanks for prompt answer. After each Blocksy (Theme + Companion) update I am flushing all LS caches. It solves mainly all problems with CSS/JS not propagated correctly. Unfortunately now it is different.

    A<span class=”HwtZe” lang=”en”><span class=”jCAhz ChMk0b”><span class=”ryNqvb”>s suggested, I looked through the LiteSpeed JS settings</span></span></span>.

    So far I had the following settings:

    JS Minify: ON

    Combine JS: ON

    JS Combine External and Inline: ON

    Delay JS load: Delayed

    When I disable Combine JS the error in Firefox console (version 123.0.1) is gone and everything is working correctly. However If I check the console in Chromium (version 122.0.6261.94) cookies consent extension is not showing up and I am getting following error:

    93d70b37165a75664928d9761a1416c4.js?ver=416c4:8 Uncaught ReferenceError: ct_localizations is not defined
    at p (93d70b37165a75664928d9761a1416c4.js?ver=416c4:8:4695)
    at s (93d70b37165a75664928d9761a1416c4.js?ver=416c4:8:5102)
    at 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8:5207
    at 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8:5271
    at 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8:5274
p @ 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8
s @ 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8
(anonymous) @ 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8
(anonymous) @ 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8
(anonymous) @ 93d70b37165a75664928d9761a1416c4.js?ver=416c4:8
91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:1 Uncaught ReferenceError: ct_localizations is not defined
    at 989 (91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:1:28771)
    at o (91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6:1636)
    at 3409 (91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:1:10641)
    at o (91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6:1636)
    at 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6:4515
    at 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6:4541
989 @ 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:1
o @ 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6
3409 @ 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:1
o @ 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6
(anonymous) @ 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6
(anonymous) @ 91dfc326dbafce4433c943caf8dac4cd.js?ver=ac4cd:6

    I need to disable Delay JS load to get rid of above error in Chromium console. After that cookie consent is working also on Chrome/Chromium browser.

    Could you please check it on your end and eventually provide a fix so the JavaScript code related to cookie consent extension can be combined and delayed in LiteSpeed cache?

    Hello @septero

    I can confirm that this should be fixed in tonight’s update. You should be able to use all of these options turned on going forward. ??

    Thanks.

    Thread Starter septero

    (@septero)

    Hi @eduard,

    Thanks for the answer. I will wait for the update ??

    Thread Starter septero

    (@septero)

    New Blocksy version (2.0.33) has fixed the issue. Problem resolved.

    Thanks for support!

    Of course, @septero. ??

    Have a good one!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Errors from Blocksy (2.0.32) Cookie Consent extension’ is closed to new replies.