I am finding the same problem! I love the plugin, but it seems to be at least an hour off! When looking back at the questions, the imprecise timing seems to be a prevalent topic. Please help…it’s a great plugin that I would like to use often! Thank you
Thread Starter
ubgaia
(@ubgaia)
We’ve also experienced it. Is there any way to fix or bypass it?
Plugin Author
Baden
(@baden03)
People: We can not help trouble shoot the issue if we can not see it running on your setup. This is traditionally done by providing a LINK to the page, as it exists live online.
With out a link, we can only guess. Here is a guess:
You are using some kind of caching plugin or CDN, so that when the plugin calculates the time between NOW and LAUNCH, the value for NOW is a cached date and time, not the actual date and time.
Thread Starter
ubgaia
(@ubgaia)
You can see it watching http://gaia.ub.edu/wpbeta/
Leave it for, let’s say, half an hour.
Then open a new tab/window loading the same page, and you’ll see the diference.
By testing other countdown timers, I discovered that several let you set your timer using GMT + or -. Once I added 6 hours (for US Central time zone), it fixed the big problem. I have 3 timers in the left sidebar of http://www.executivetm.com. Yours is the top one, the other two are below the map. You can see that the hours are now adjusted, but that your timer is a few seconds slower than the other two. Will you be adding a GMT adjustment to your timer, or have I missed it? Thanks!
Plugin Author
Baden
(@baden03)
1. Adjusting for local time is based on the timezone settings of your WordPress install. Please verify that your timezone settings are correct under:
Dahsboard > Settings > General > Timezone
2. As for the difference in seconds. This is because our plugin waits until after the page has fully loaded before it starts to count down. However, you make a valid point. We will look at improving this for the next update. Thank you for the feedback.
3. Regarding the clock not being accurate over a 30 minute viewing we will address this along with the issue above in our next update.
