Wow, the beast rises again! Actually, one of the last posts I did as a CT member was to alert the CT on the issue and the fix. As a side note, javascript solutions will not work in all cases, but the bigger issue to me is that using javascript to take the machine's time still doesn't get us to a solution for providing support for historical references with regard to date/time. Think of the many times a record has a date/time associated with it, and how that is being stored. Just to simplify it by addressing only the 'display of the current date' is less than a solution IMHO.
The fix to the CurrentDate display does help in some ways, so I created a document of how to do it, and mentioned it on the forums. I even emailed it to several folks, who followed the example in the doc and subsequently thanked me.
Now, I'm still working out the nitty gritty of doing something about the whole date/time issue, but there's just never enough time or dates to get things done the way I'd like. Family comes first, then Day gigs , and my pet projects like DNN, and sorry but that's just the way it is for me. (And why I had to leave the CT.)
The issues that remain include the general use of date/time information in the core and 3rd party projects. My feeling is that DNN or any web app with a global community target audience needs to embrace using UTC for storing date/time information. What we have now is really a confusing array of imcomplete solutions to the accurate storage and display of date/time information. The many changes coming up for folks in Aus, USA, Canada, and others really pinpoint the need to address the issue, not only for DNN but MS has not done their part in providing any solution. The registry does not provide much more than a simple display for the current year. Talk to anyone in AUS about the changes they've had to make regarding the Commonwealth Games, and Summer Time transition dates, and those kind of changes will need to be reversed next year, and you'll see what kinds of issues are being felt. If you're hosting a AUS client, you should have dealt with the issues as well, but I find many are not keeping up with the registry timezone changes, because they are not part of a regular MS update. I guess the feeling is if you're not from a particular area where the tz registry entry is changing, you don't need to worry about it. That is just wrong, especially in our gloabally expanding use of the Internet.
Anyway, just my thoughts, which are not intended to imflame or discount anyone, just trying to get the issue some attention...