Cached pages always start from same time

One workaround until this is fixed is to add a line at the top of uji_countdown.js (before everything else):

if (ujiCount.uji_utime) {ujiCount.uji_time=new Date().toString();}

This enforces using the user’s time (from Javascript) rather than the server time if that setting is checked.

That’s funny. I don’t get that behavior on http://www.naespconference.org (tried Chrome, Firefox, Edge, and IE, all on Windows set for US English).
I don’t know whether the difference from what you’re seeing is a result of the Uji version (I use 2.0.8), the browser, the OS, the language setting, or some configuration in WordPress. I’d be curious to know whether the “59 seconds” thing happens when you browse http://www.naespconference.org.

It sounds, though, like somehow your system is always getting 0 for the seconds field when it generates a date. Were you always starting at 59 before you added the extra line to the JS?

This page shows you what your system (browser, OS, locale) gives for the toString() method. https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_tostring Does it show seconds?

• This reply was modified 7 years, 7 months ago by naesp.