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 ForumsFeedbackFeedbackIncorrect time of the message..Incorrect time of the message..
Previous
 
Next
New Post
5/14/2008 1:19 PM
 

David,

you will need to modify the source code. Besides, please log the issue (and your fix) to the public issue tracker at support.dotnetnuke.com, thank you.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/10/2008 2:17 PM
 

Hi Sebastian,

Can you tell me how to modify this from source code directly?

 

Thank you~~

 
New Post
6/15/2008 5:34 PM
 

Eric - you wouldn't be able to modify it from the source code itself. When a feedback is created, the system is using the date/time on the database server to set the createdate value. One way you could do it in the code is to modify the viewcomments section and transform the createdate to whatever the corect date/time is in your timezone but this would be a "hack fix". The real fix needs to be done at the sproc itself where I pass in the create date as part of the parameters. I have this on track to be included in 5.0.0 once i finish up the rest of the to do's for that version..


Sanjay


AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
6/16/2008 3:56 AM
 

Sanjay,

I am sorry, that I have to disagree, but I spent some time on this subject when evaluating options to implement DST support in the core for DNN 5.x.

Most modules - even in the core - deal incorrectly with timestamp values by usually deriving it from SQL Server using GetDate. There are several issues caused by this practice:

  • timestamps will remain unchanged, when server time zone is changed (e.g. for DST turned on/off)
  • there might be differences between sql server and web server time, and any comparison with current time on the web server will be inacurate (e.g. for search indexing)
  • timestamp in "createdAt" field, autmatically set in AddItem stored procedure cannot be kept during Export/Import

Therefore my advice to all module developers:

  • Always store timestamp values in UTC and convert to appropriate user time zone when displaying the value to the user. Due to current limitations of DotNetNuke, the time displayed will be offsetted by an hour during DST.
  • Always create timestamp on the web server and pass to SQL to avoid inaccuracies and be able to keep it

The issues listed are of minor relevance for Feedback module, but should be regarded as best practices.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/16/2008 11:54 AM
 

Sebastian - good post and thanks for the heads up... I was going to look at one of the existing modules to see if I could get the proper direction before attempting to make the fix :)... I do understand about UTC and was planning to address it similar to what you've mentioned (ie creating timestamps on the web server and passing it to SQL)...

I'll touch base with you to go over my proposed fix but I think we're on the same page :)

Thanks again
Sanjay


AcuitiDP - Oracle Data Provider for DotNetNuke
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsFeedbackFeedbackIncorrect time of the message..Incorrect time of the message..


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