I have been thinking a lot about the time zone issues.  I have wrestled with this issue alot.  I've been thinking about ripping the Event Time Zone back out.  If you think about it, user's should expect events (unless it is their own private calendar) to display in the site set time zone.  Therefore for all event calendar instances, no time zone would be displayed for views of events.  All events are assumed in the site time zone.  If user's wish to convert to another time zone, we might have a selection/dropdown to allow them to review the events in their preference.  Also, this lends itself to a future planned enhancement: Per User Event Calendar Instance...this would provide each user with their own calendar instance, in their preferred time zone and would fit more with the DNN model.  User's would then be able to reference other, resource calendars (and other user's calendar, if permitted) and display the events in their preferred time zone.  I believe this model of Event Calendar Time Zones is more supportable and more understandable.  Your thoughts?  Issues?

Thanks!

I have a couple  of thoughts (more or less in random order, despite the numbering ;) )

1. if anyone goes to a website, sees a calender, sees an event, with location, date and time, I am sure anyone would assume that the date and time would be the local date and time for the location of the event.
2. if the event is an online event (for instance the core team chat event, every wednesday 3 pm pacific time), visitors would likely want to convert that date/time to their own time zone. I know i am 9 hours ahead of Seatle, but i still have trouble actively calculating my local time from that difference (its midnight of course)
3. if there are multiple international (different timezoned) events added to the same calendar, I'd expect each event to be displayed in the timezone of the location
4. if i import the event in my outlook, surely i expect the date/time to be my local date/time, not the date/time of the event location
5. Usage of different timezones is especially difficult, because of the daylight savings differences between countries, which means that 3) will be very difficult to implement. I think timezones like this should be handled by the core. FYI, this has been discussed before on ASP.NET, see for instance these threads:
   http://forums.asp.net/1171827/ShowPost.aspx, http://forums.asp.net/thread/961423.aspx, http://forums.asp.net/896413/ShowPost.aspx
6. My vote for now would go for a system that at least works correctly, and readd event module specific timezones in a later version maybe.
7. What would work for me is the same setup as the forums module. Date/Times of forum posts are shown in the timezone of the logged on user, and in the timezone of the portal for the anonymous user. I agree with Alan that one might expect events to happen in the timezone of the portal. I think you will catch about 95 % of all use cases

do i make any sense ?

DNN Blog | Twitter: @erikvb | LinkedIn:

Hey Alan

I'm not sure if this is the right spot for this but here goes

It is time zone/format related

My dnn site is set to EN-AU default short date is dd/MM/yyyy

when I choose a date from the pop up calendar the format in the text input field shows as MM/dd/yyyy

I get endless emails about that - could you format the date in long format - I think that would end a lot of confusion

you would see friday, march 5 2007 instead of 3/5/2007 so the humans would not be confused and the browser would have no trouble parsing the date no matter where you are from

second if I enter an event say 26 feb till  6th march youu can see the event on the feb calendar but it is not displayed on the march calendar at all

if you follow the link there is an example with events that go from feb to march and marh to april http://hoster.coffs.com.au/AVCalendar/tabid/432/Default.aspx 

The code to display the next month works but that it may be a date format problem which prevents display of events that start in the previous month

Regards

Wayne Irving