Hi @julienallard1 (also @rio): This is apparently a bug in the Bubble plugin editor (which has surely broken many simple plugins). I’ve fixed the issue for Browser Timezone and Locale by moving state publishing up to the code initialize level, instead of relying on Bubble’s “state initialization” routines.
To fix, just update your Browser Timezone and Locale plugin to version 1.1.0. (And post here if you have any additional problems.)
Sorry to hear that this has been broken for so long. I’ll be posting a rant and reporting this formally to Bubble. Shit like this pisses me off.
Detail for bug report:
All this plugin does is stuff like:
Open your browser console (hit F12) and enter this command:
You’ll see the time zone returned properly.
So, what seems to be happening is Bubble plugins are not calling their state initialization routines – or at least, not all of them.
(Since most plugins, with some notable exceptions (e.g., my advanced plugins), use these techniques it’s fair to say that pretty much all basic Bubble plugins are broken right now. Surprise, surprise, right? This would seem to be yet another very serious Bubble bug that apparently nobody bothered to report.)
@allenyang @eve and whoever, take note
You can see this quite clearly as here’s a version of the Browser Timezone & Locale plugin that prints console logs whenever any of the initialization routines are hit:
But in the console, all we see is:
So, as you can see, only the last initialization routine is being called (they should all be called)… and that routine is somehow being called twice. Nice, right?
Anyway… ranting aside… to fix your issue, upgrade to version 1.1.0 of the BTZ&L plugin. But, again, this isn’t MY bug, it’s a Bubble bug.