Timing error since last update
-
Hi, there was an update yesterday of this plugin. I noticed at 23:00 CET that “today’s” stats such as visitors and visited pages was reset to 0, to start a new day. Previously that was at midnight. Something went wrong there. WordPress clock is set to CET.
-
Hi @webwitnl,
Thanks for reaching out. We’re looking into it. We made some changes to the time zones recently and it looks like the WordPress time zone might not have been matching up with the data on the dashboard.
From what we can tell, it looks like the problem may have been caused by the Burst Statistics caching. After you updated Burst, it looks like the cache wasn’t cleared automatically and that might have caused the time zones to be off.
But we’re pretty sure this won’t happen again tonight. Just to be sure, we’re gonna run some tests today and let you know how it goes.
Kind regards,
HesseHi @webwitnl,
We have investigated the issue. I can confirm that the chart does not show the correct time sometimes. This happens when the server time is not in the UTC timezone.
We’ll work on a fix for this issue. We have a small team and I’m primarily responsible for Burst. I’ll be on a one-week holiday from tonight on. So we will probably not have a fix ready in the upcoming week. Sorry for the inconvenience. I’ll get on it right away when I’m back 🙂
Kind regards,
HesselThanks. Please note the server time is definitely in UTC. It’s now 14:13 CET. Server:
>date
Fri Jan 20 13:13:06 UTC 2023
Thanks for the additional info. Could you look into the console and share all the time information from there?
-
This reply was modified 3 years, 4 months ago by
Hessel de Jong.
Are you referring to the browser console? It shows CET time, it’s just the time my OS is running in.
Yes I’m referring to the browser console. Are you on the latest version of Burst? There should be some debug data in the console.
Ah yeah I see it now. It’s now 15:51 CET and console gives:
dateRange:
Object { startDate: “2023-01-13”, endDate: “2023-01-19”, range: “last-7-days” }index.js:382:578682
gmt_offset: 1 index.js:382:578711
sql_timezone: SYSTEM index.js:382:578765
wp_time: 1674229894 index.js:382:578823
server_time: 1674226294 index.js:382:578871
sql_time 2023-01-20 14:51:34 index.js:382:578927
sql_time_utc: 2023-01-20 14:51:34 index.js:382:578975
device_time: 1674226295958 index.js:382:579033
device_timezone: Europe/Amsterdam
Thank you for the information. We’ll look into it and I’ll let you know when we have fixed the issue.
Thanks a lot for the trouble.
Kind regards,
HesselHi @webwitnl,
Thanks for the patience. I think I found the issue. The mySQL query that selects the data from the database formatted the time based on the server time. For you this was presumably +01:00(CET).
I have made a fix for this on our GitHub. Can you please try it and let us know if this fixes your issue: https://github.com/Really-Simple-Plugins/burst/tree/1.3.4_Timezone_issue_fix
Thank you for providing all this information so we could make a fix.
Kind regards,
HesselCan I just download the whole thing on github and replace the burst-statistics directory with that? Or otherwise let me know which exact files I need to copy.
Hi @webwitnl,
Yes, you can download the whole directory. Unfortunately, we are not allowed to share ZIP’s on the forum.
- You can click the Green ‘Code’ button.
- Click on Download ZIP
- Unzip and change the folder name to ‘burst-statistics’.
- Either you can rename you’re current ‘burst-statistics’ folder to something like ‘burst-statistics-old’ and upload the new folder.
- Or you can ZIP the folder downloaded from GitHub again and upload via the WordPress Admin. It will ask to replace the existing folder and you can just replace.
Hope this helps!
Kind regards,
HesselHi Hessel, unfortunately that did not fix it.
The mySQL query that selects the data from the database formatted the time based on the server time. For you this was presumably +01:00(CET).
Please note that the server and everything running on it is in UTC. Only WordPress is set to CET.
Hi @webwitnl,
Sorry to hear that. I have reproduced the issue and I’m quite sure this should fix the problem.
Can you try and install this version from our GitHub?
https://github.com/Really-Simple-Plugins/burst/tree/1.3.4_23_00_timezone_fixHope this was not too much of an hassle.
Kind regards,
HesselThanks, I installed the new version and will let you know how it works out.
Thanks for the patience! I really hope this is fixed 🙂
-
This reply was modified 3 years, 4 months ago by
The topic ‘Timing error since last update’ is closed to new replies.