We had a recent topic about this (BST) but I thought I’d start a new clean one to highlight the actual problem.
The date/time stamps on reflector posts are correct (and are UTC).
The error is in the age of posts to the reflector. A newly posted message shows up as 60 minutes old.
I suspect the server “time interval” code is using “times recorded in UTC” and it’s subtracting that from “local time now” to get the age. This works when localtime equals UTC but gives the wrong answer when localtime moves to DST.
This is an old problem I first noticed it this time last year.
I’ve been elsewhere, a rally and an AGM plus the usual full-time work. Perhaps GM4ZFZ would like to elucidate on exactly what was wrong since we all hope it’s properly fixed so it doesn’t break again next time the clocks change like it di this year and last year.
Don’t bother your head about it, Colin, its a trivial irritant usually fixed quickly and so far has not warranted the effort to permanently remove it with so many things of higher priority to be done.
Perhaps GM4ZFZ would like to elucidate on exactly what was wrong since
we all hope it’s properly fixed so it doesn’t break again next time
the clocks change like it di this year and last year.
It’s just a particularly bad bit of code which I hacked into place seven or eight years ago which takes about 30 seconds to change twice a year. Sorry, I just haven’t got round to doing it properly. Sorry!
It’s just a particularly bad bit of code which I hacked into place
seven or eight years ago which takes about 30 seconds to change twice
a year. Sorry, I just haven’t got round to doing it properly. Sorry!
No problem, however I think that means that Andy MM0FMF owes me an appology for his condescending post earlier in this thread.
And knocking SOTA MT volunteers who have other lives outside of SOTA is not very constructive Colin! Things always get done in due course which to me is acceptable when it happens.
Guys, remember "Think before you post!"we require posts to be “appropriate, constructive, friendly etc etc” but this thread is heading into unfriendly territory, so I now declare it closed.
