Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsEventsEventsTime issues with Export Event to Desktop EventTime issues with Export Event to Desktop Event
Previous
 
Next
New Post
3/16/2007 3:58 PM
 

I am not sure this is Event Module related.  But I am curious if anyone has any insights.

I am having this problem with both the latest Event Module Release and the Event Module Beta.

I can create appointments no problem.  They show up correctly on the calendar, correct time, everything..  However, when I go to "Export Event to Desktop Event" and add the event to Outlook the time on Outlook is one hour later than the time of the event.

 

Thanks in advance for the help,

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
3/16/2007 4:05 PM
 

Hi.  This has been a problem since Day 1.  It's because we are now in Daylight Savings Time.  For some reason, the export feature doesn't take Daylight Savings Time into account.  The good news is that the export time will be accurate again as soon as November arrives!  LOL!

If I remember correctly, Alan said that this is because the export procedure calls on a core DNN function that doesn't recognize DST.  He might have rewritten the beta version of the module to work around this problem, but I'm not sure.

See Ya,
Van


See Ya! Van
 
New Post
3/16/2007 9:49 PM
 

The event module exports the event (vcs) file as UTC +0 offset.  The local calendar (ex. Outlook) is responsible for converting this date/time to the correct local time.  So, this would most likely be an issue on the local (registry) database....not the events module (since it is in UTC offset 0 format).

The beta version has not fixed this problem...DST is not accounted for in the DotNetNuke TimeZone tables.  I am working to try and get the core team to correct this and update the DNN TimeZone tables w/the DST offsets.

 
New Post
3/19/2007 3:12 PM
 

favance,

I am a bit confused.  The first paragraph seems to indicate that this is a problem with Outlook, however, the second paragraph seems to point to DNN.  Where should I be looking to resolve the problem?

 

Thank You,

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
3/19/2007 8:56 PM
 
I'm not sure you can resolve the problem.  DNN has a TimeZone offset file...  That's what we are using in the Events module.  I natively assumed that this would work when I started coding for TimeZones...it does not.  In addition to the fields in the TimeZone fields in the XML File, we need a DST begin/end date/time fields and offset.  There are several great web articles on the issue.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsEventsEventsTime issues with Export Event to Desktop EventTime issues with Export Event to Desktop Event


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out