Button does not open in safari when no analytics is confirmed in cookie banner

Patrick_R

Hello,

we have a problem on our website that the buttons do not open if you do not accept Google Analytics in Borlabs Cookie Banner. But we have disabled Google Analytics in Buttonizer. Why does it happen?

In Safari it shows the following error code: "Can't find variable: dataLayer".

I hope for your help, thank you very much!

Jasper

Hey Patrick!

Thanks for reporting this issue!

That's odd, of course that should not be happening. Buttonizer should skip that if the variable is not set.

Can you let me know on which site this is happening? Then we can take a look at what's going on and fix that in an update.

Hope to hear from you soon 🙂

Patrick_R

Hello Jasper,

Thank you very much for the feedback. The problem occurs on our website https://kundenwachstum.de/.

When you open the page and click on "Auswahl speichern", Google Analytics is deselected and then the error occurs in the Safari browser.

Best regards
Patrick

James

Hi Patrick,

Thanks for the link to your site and the info.

It looks like Buttonizer is currently not enabled on the site. Is it perhaps possible for you to activate Buttonizer again?
We would like to take a look at the Buttonizer button and test it out and find out what's causing the issue. 😄

Patrick_R

Hello Jasper,

sorry, I had tested something else. Now it is back again.

Best regards

Jasper

Patrick_R Hey, just want to let you know that we're working on a fix! We'll update you when we've deployed an update later today 🙂

Patrick_R

Hello Jasper,

Have you already solved the problem?

Best regards
Patrick

Jasper

Hey Patrick_R , hope you've had a great weekend.

We have just deployed an update to our standalone with the fix. Let me know if this fixes the issue 🙂

You might need to clear the cache before seeing the changes (or view in incognito).

Patrick_R

Hello Jasper,

Thank you for the feedback and the quick adjustment. Yes it works now!

Will you provide the updates only for the standalone or also for the other version?

Best regards
Patrick Roso

Jasper

Hey Patrick_R , apologies for the delay in our reply and thanks for replying and letting us know the issue has been fixed.

Currently a lot of code in our standalone (the frontend as well the editor) has changed compared to our previous WordPress only code (version 2.9 and before). We added quite a lot of new features since version 3.0 and removed deprecated code (minimalizing our bundle size).

I think we'll update our legacy code eventually in the future, but currently our focus is on developing new features for our standalone first.

If there's anything else we can help you with, make sure to let us know! 🙂