hmm yes, that's what I also understood from Chapman's blog that I linked in the first post.

I tried setting portal 0 and then also my host portal, which is portal 18, to the server time, It didn't seem to help. Then I thought of changing the server timezone so I went and did that, and after setting everything else, portals, accounts, and all to the same timezone, I was finally able to make a blog post and have it display teh correct time. All the old posts are still wrong, but at least new ones won't be.

Then I messed around with Active Forums and found that I could also finally make it show the correct time for posts, but only when it is set in it's own options to UTC 00:00 - odd.

Next I need to figure out if my users will have correct times when they post from timezones nearby.

And if time zones now work properly, then I have to figure out why it can't do the same thing when the server is set to its proper local time.

I've been quite schocked, in my extensive searches this past week on the matter, to find the same discussions and the same issues going all the way back to the ASP.Net forums. I recall spending a few nights on the issue myself back then, and then simply shelved it. I had assumed that it must have been fixed up by now, but I guess not.

I should check that DNN roadmap and see if it is on there.

In the meantime, the server timezone change is holding up ok. The only potential issue I can see is that Active Forums, which has its own timezone setting, has to be set to GMT to give the correct timing for my location, which is GMT+12. That means that if I create a portal for someone who is located more than 12 hours behind my timezone, their forum will not be able to show the right time... because it can only be adjusted up to 12 more hours back from where it is currently set (GMT).

I have yet to check some of the other modules like Ventrian News Articles. Hopefully they'll all start behaving!

Rob