Thanks for your replies, we're glad you manage to get it working!
Sorry about the trouble when migrating to the standalone! My guessing is that it might have been the cache on your website, loading the standalone script and the WordPress mixing together.
I can ensure that the standalone IDs are static saved in the database and don't change or rotate, so it could be that the IDs were mixing up/switching between with the cached WP Buttonizer data and the standalone (which actually would be weird as the IDs should have stayed the same on migrating).
Hope it doesn't happen again. If it does, let us know, then we can investigate on this further!
UPDATE2: It's not clear what happened (the only thing I did was disconnect/reconnect to Buttonizer) but now everything is functioning correctly again. If that was one of you guys, nice work!
We actually did not do any updates yesterday 😅 Next update will probably be on next Monday or Thuesday 🙂
BTW, while you're updating the code be sure to check out some of the other events like Mousedown. It also behaves differently now, where it keeps the button open (just like click) rather than acting like a momentary switch. But perhaps that's how it's supposed to operate in the first place without the extra closing click.
Can you elaborate on this issue a little bit more? Does it behave different as soon you disable that setting in your code or in our code?
It's good to know I'm not crazy -- for a while there I was starting to wonder. 😅
Haha sorry about that! We were also debugging and staring at our code and felt the same! When testing the code via console it works like a charm, until we were using the custom click on the page itself... Fortunately we got our own little
eureka! moment and found the cause of it. Sometimes we even forget about some features we build that might collide 😛
We'll update you as soon we've updated the code and deployed it to live. In the meantime, if there's anything else we can do for you, let us know! 🙂