• Support
  • Button not working on website

Hi there,

For some reason our buttonizer isn't displaying on our website. It was yesterday, so I'm not sure what's happened in that timeframe. Is someone able to look into this? We were hoping to launch the website today.

Thanks, Gemma

  • Jasper replied to this.
  • Hey gemmayoungman ,

    First of all, welcome to the Buttonizer Community!

    I've checked your site and found the cause of the issue. Since you changed the domain name (perhaps from staging to production), it didn't match our cached data (where the widget decides it's allowed to become visible).

    I've resetted the cache for your site and it's now loading in propperly! Can you verify this on your side as well?

    Hope to hear from you soon! 🚀

    Hey gemmayoungman ,

    First of all, welcome to the Buttonizer Community!

    I've checked your site and found the cause of the issue. Since you changed the domain name (perhaps from staging to production), it didn't match our cached data (where the widget decides it's allowed to become visible).

    I've resetted the cache for your site and it's now loading in propperly! Can you verify this on your side as well?

    Hope to hear from you soon! 🚀

    Hi Jasper,

    This is great, thanks for replying so quickly! For future reference, can I ask what the solution was to this?

    Thanks, Gemma

      Hey gemmayoungman !

      Awesome! Thanks for letting me know and no problem! 🙂

      When a site is deployed and is being visited by vitors, we're caching quite some data to deliver content all across the world within milliseconds and make sure to backend doesn't get overloaded. This means, when you make a change, it can take a minute before they're visible on your site.

      In this case, our CDN cached a result from a domain that wasn't allowed to load in Buttonizer (perhaps it was when the development domain was still set up?). So I made sure the domain was set up propperly (which it was) and force-cleared the cache for your widget on our side, so on the next request the cache will be refilled with the correct result.

      Unfortunately it was a bug on our side. However, it's good to know that the issue would resolve itself since the cache will expire eventually 🙂