I'm sorry to spoil the party, but...I just downloaded your Events_3[1].2_Install.zip file from DotNetNuke and installed it on my DNN 3.2.1 site.  I made sure the host settings had the correct time zone before I uploaded the module.  I now have everything defaulting to UTC - regardless of how I set it when I create the event.  This is while I am logged in.  I have it on a test page so I cannot see it if not logged in.  Any ideas?

UPDATE:  The time zone in my user profile was set wrong.  I will need to notify all my users to check their profile and change the time zone - or they will be seeing what I see!  Thanks for the tip!

Here's how the Module Event Timezones work:

Add/Edit Event:  Defaults to the TimeZone set for the user adding the Event (can be changed and is recorded with the Event

View Events (including Month View, Week View, Detail View, List View):

1. Anonymous User:  Uses the default Site TimeZone (see DNN Admin Menu -> Site Settings -> -> Advanced -> Other Settings -> TimeZone)
2. Registered User: Uses User's TimeZone (select logged on User Profile and change TimeZone)
3. Admin User: same as Registered User

For all Views, the TimeZone is converted from the Original Edited Event to the User's default (see 1-3 above).

Upgrades:  Set the Registered/Admin User's TimeZone before upgrades to existing Events (or AVCalendar) data.  This TimeZone is used for the upgrade of existing Event Data.

This has been tested using DNN 3.2.2 and DNN 4.0.  The module also works and has been tested in at least 2 other languages.

THIS IS A COMPLEX MODULE and has many features.  Hopefully we will have some documentation soon (does anyone want to step up to the plate?).  Others have tested and localization and timezone conversion does work when the module is setup on a properly configured DNN site. 

Finally, the Source Code has been delivered and you are encouraged to study it, use it, enhance it, or whatever.  If you find issues/fixes, please share them with us.

thanks for your support,
    Alan