Button not showing up & plugin not GDPR-compliant

  • Resolved chris29888

    (@chris29888)


    2 years, 4 months ago

    I just installed Buttonizer on a customer’s website. I’ve used the plugin in the past and it always worked. But now, after setting up everything, the button simply doesn’t appear EXCEPT while I’m using the WordPress customizer.
    Chrome’s developer console displays this error message:
    (index):2600 Uncaught TypeError: Cannot read properties of undefined (reading 'init') at (index):2600:19

    Clicking on this message shows the following code:

    <script type='text/javascript' id='buttonizer_integration_script-js-after'>
window.Buttonizer.init('38832ff7-def7-4d40-9ddb-767436436830');
</script>

    The part “init(‘38832ff7-def7-4d40-9ddb-767436436830’);” has a squiggly red line under it.

    Any idea what might cause this?

    The second issue is that the plugin isn’t compliant with the insanely annoying requirements of the EU’s GDPR.
    Opening Chrome’s developer tab “Sources” shows that there is a connection to cdn.buttonizer.io being established in the background. This type of behavior is pretty much illegal and there are tons of vulture lawyers scouring the internet for these exact issues.
    I’ll have to deactivate the plugin as long as this isn’t “fixed” because it might end up causing us a lot of trouble.

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

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Buttonizer

    (@buttonizer)

    Hey @chris29888 ,

    Thank you for sharing your thoughts and concerns! Our apologies you feel like this as a long-time user of our plugin.

    Regarding GDPR compliance
    We are a Dutch company, so I can assure you that we do not collect or store any personal data of website visitors connecting to our server and showing floating content. We don’t store any visitor logs and don’t track visitors via cookies.

    Of course, as a European company we have to be GDPR compliant as well and are careful with working with third parties.

    All user data of site owners registered to our dashboard are only being used to provide the service. The DNS and CDN is provided by Cloudflare. Cloudflare is GDPR compliant and has a page with information available.

    I don’t think we have this written down on our site at the moment, so we’ll have a page up soon that will have all the necessary information available, such as what we do to be GDPR compliant and how we protect our customers (and your visitors) privacy.

    The other issue
    The issue you have sounds like you might use a caching plugin which might defer our embed.js script to load the Buttonizer buttons.

    Are you able to let me know if you’re using a caching plugin and if so, which one it is? If not, was it properly loading in the embed.js?

    Hope to hear from you soon, then we can take a look at it further for you ??

    P.S. You can also contact us via our Buttonizer Community via opening discussion or a private ticket

    Thread Starter chris29888

    (@chris29888)

    Hey, thanks for the detailed response!
    I’m no legal expert, but I’ve heard multiple times that as soon as one of those background connections is established, no matter how compliant the company at the other end of the line is, there needs to be a clearly indicated consent by the visitor because their IP is still being transferred to some external domain that isn’t the one they’re visiting right now. In theory this could enable the company behind the hidden connection to do whatever shenanigans are possible by knowing someone’s IP and time of access.
    (Again, not a legal expert, but that’s what I’ve come to understand.)

    The other issue
    Unfortunately, there are no cache plugins currently running on the site that could mess with Buttonizer’s functionality.

    Plugin Author Buttonizer

    (@buttonizer)

    Hey @chris29888 ,

    Thank you for taking the time to reply again! Really appreciate it ??

    Regarding loading in Buttonizer
    I think you’re making good points there and we’re currently researching how we can improve this so we can release an update next week.

    We’ll try to lazy-load Buttonizer until someone agreed to the GDPR-plugin of choice. The only issue might be that there are so many different GDPR-plugins. So, we’ll investigate on it so we can build something propper.

    Could you perhaps let us know what plugin you are you using? Then we can take a look how to help you further.

    The other issue
    Thanks for this information. We might have found the cause of the issue and have released version 3.0.3 that should fix your problem. So, if you want to retry again in the future, this issue should have been resolved.

    Hope this helps and to hear from you soon again, enjoy your weekend ??

    Thread Starter chris29888

    (@chris29888)

    Wow, thank YOU for being this reactive!
    I just installed 3.0.3 and it actually does work and the button is now appearing on the page (still disabled it again because of the GDPR stuff that I’m still not sure about).

    For the whole cookie consent stuff I’m using Borlabs Cookie.
    It seemed to be the most competent and expansive consent plugin and it’s been doing a great job over the past years with constant updates to keep up with the ever changing clusterf*ck that is the GDPR.

    Thread Starter chris29888

    (@chris29888)

    Any news on the GDPR front? Buttonizer still connects to cdn.buttonizer.io in the background without giving me the option to disable this / only establish the connection if the user opts in.

    Plugin Author Buttonizer

    (@buttonizer)

    Hey @chris29888 ,

    Hope you’re doing fine. Thanks for revisiting this question and bringing it back up.

    Apologies for not getting back to you any time sooner. To be honest, we hadn’t thought of any solution until last week.

    The following solution is what we have in mind
    We’ll add a switch to our Buttonizer plugin settings to only load in Buttonizer script in the frontend when a specific parameter is set for these situations.

    This parameter should be triggered via the plugin that manages the GDPR/Cookie part. Does Borlabs cookie also support executing some JavaScript when giving consent via the admin dashboard? Or only using their JavaScript API?

    New GDPR information page available
    Since my last reply, we now have also added a GDPR page where we try to answer all kind of questions, such as what data is being collected and what not.

    You can check out this page here: https://buttonizer.pro/gdpr/

    We’ll soon update our plugin and link to our GDPR there as well.

    Let me know what you think ??

    Thread Starter chris29888

    (@chris29888)

    Hey, thanks again for getting back to me so quickly!
    That sounds great. Borlabs allows the execution of custom JS after a user has given explicit consent, so it shouldn’t be a problem.

    Still though, and this might be a stupid question, given that I’m not a developer, isn’t it possible to locally embed the 2 files that are currently being loaded via the external CDN? (embed.js and frontend.css)
    Wouldn’t it be enough to connect to the Buttonizer servers only while making changes to the currently implemented buttons and then have them create 2 static, local files once the WordPress admin clicks “Save”?

    Plugin Author Buttonizer

    (@buttonizer)

    Hey @chris29888 ,

    Thanks again for taking the time to reply. Great to hear that, then I know we’re heading the right direction! We’ll try to update the plugin soon.

    Still though, and this might be a stupid question, given that I’m not a developer, isn’t it possible to locally embed the 2 files that are currently being loaded via the external CDN? (embed.js and frontend.css)

    ‘Stupid questions‘ don’t exist ??

    This is actually (sort of) possible: there are a few caching plugins like WP Rocket that do cache external files from CDNs. The only thing is that from time to time you’ll need to clear the cache as the cached files will stay behind the updates we push to our CDN.

    In that case only the API is the part that is that hit our server.

    However, I think the JavaScript solution is the easiest and best way as it won’t import our JS until consent has been given.

    Wouldn’t it be enough to connect to the Buttonizer servers only while making changes to the currently implemented buttons and then have them create 2 static, local files once the WordPress admin clicks “Save”?

    In some situations, there’s some backend logic on our side which handles the callback before generating the widget list (for example, how the widgets perform or when/where buttons should be visible).

    Thread Starter chris29888

    (@chris29888)

    Alright, thanks for clearing that up! Looking forward to the update.

    Plugin Author Buttonizer

    (@buttonizer)

    Hey @chris29888 ,

    Good news! We’ve released version 3.3.0 with a new plugin setting called GPDR: Wait on consent. No requests will be made until a function has been called from any GPDR-plugin.

    We have more information about the functionality on this page: https://community.buttonizer.pro/knowledgebase/1426

    Are you able to try it out and let me know what you think? We did add some Borlabs cookie steps, but I am not very sure how accurate they are.

    Hope to hear from you soon!

    Plugin Author Buttonizer

    (@buttonizer)

    Hey again @chris29888 ,

    I was wondering if you have seen my previous reply? Hope to hear from you soon ??

    Thread Starter chris29888

    (@chris29888)

    Hi!
    Sorry for not replying sooner. It sounds really amazing and I’m already super thankful that you addressed this issue.
    Unfortunately, I still haven’t had the time to implement the latest updates cause I’ve been swamped with work for the past few weeks. I’ll let you know as soon as I try it out!
    Thanks again!

    Plugin Author Buttonizer

    (@buttonizer)

    Hey Chris,

    Thanks for your reply. No problem at all ??

    I’ll mark this topic as resolved for now, but make sure to update us when you try it out. We’re really curious if this actually solves all your concerns and if you have any feedback left.

    In the meantime, if there’s anything else, make sure to let us know or open a ticket ??

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Button not showing up & plugin not GDPR-compliant’ is closed to new replies.