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

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...CurrentDate - is what date?CurrentDate - is what date?
Previous
 
Next
New Post
4/13/2006 11:52 AM
 

 

You don't need to worry about the difference between the server and the client with regards to DST.

It is always an offset based on what the current date/time is on the users machine.

The registry settings and the fact that rules change for DST are all moot if the offset is calculated at runtime.

Example:

User A from Pluto makes a post in the forums and the server is on Mars using MLT (Mars Local Time).

The server on Mars stores the post in it's system after first converting it's local time to UGT (Universal Galactic Time).

User B from Earth comes along and wants to read the latest post by User A.
       When User B requests the page, their browser sends an offset (calculated from their current local time in relation to UGT).
        The Server then takes this offset and applies it to the date/time it had stored for the initial post so it can return that information to User B relative to their current local time.

Now, let's say that same User A wanted to come back 10 years later and Pluto had adopted a new time system because a new planet had been dicovered next door to them that had really cool clocks.

User A would send their new offset from UGT to the server, and the server could show them when their old post was made in relation to their new way of keeping track of time.

In other words, it's all relative.  If you fix the point of reference, then all other points can be expressed relative to that fixed point.


DotNetNuke Modules from Snapsis.com
 
New Post
4/13/2006 12:12 PM
 

Good one.  So, when can we expect it to be fixed in Core?  Will the solution work for server to portal time differences?  Is that going to get the localization complete for folks using different calendars?

Please, post a working example, so we can see it and evaluated it.  Really looking forward to the issue going away before my time on this planet is done. :)

 

 
New Post
4/13/2006 2:09 PM
 

Q: So, when can we expect it to be fixed in Core? 
A: If there is a bug in the core, it will get fixed after it is identified and recorded in Gemini. I know the main problem that this thread was created for has been identified and recorded.

Q:Will the solution work for server to portal time differences?
A: Yes. Refer to my previous post in this thread.

Q: Is that going to get the localization complete for folks using different calendars?
A: Maybe you are talking about a different issue.  Please start another thread if you are having an issue with localization of calendars.

The working example is in the link I posted earlier.  http://www.dotnet247.com/247reference/msgs/37/188110.aspx


DotNetNuke Modules from Snapsis.com
 
New Post
4/13/2006 3:52 PM
 
Maybe someone can come up with an alternative 'Current Date' skin object that can be used in the meantime or for older versions (or at least ver3.x +) of DNN with out having to modify the core?
Antony
 
New Post
4/13/2006 4:27 PM
 
The only way to do this would be to use JavaScript or write the correct code without making use of all the core features. Heck, if you want, just add the JavaScript to the skin - there'd be no need for a skin object.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...CurrentDate - is what date?CurrentDate - is what date?


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