Hello,

on DNN 4.0.7 and 4.0.8 (different servers) I'm facing a strange problem with the DNN:CurrentDate skinobject: it shows the wrong time, from when we changed to DST.

I have Site Settings and User settings bot on UTC+1, but CurrentDate still shows the old hour (1 hour late: if it's now 17:50, it tells 16:50). I also see there was a bug (http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=2787&PROJID=2), but it's closed... what am I missing?

Here's how I define the skinobject in my skin:

<dnn:CURRENTDATE runat="server" id="dnnCURRENTDATE" Dateformat="dd MMMM yyyy HH:mm" />

 Thank you,

al.

DNN does currently not support DST, users and  admins need to adjust timezone settings.

Sebastian Leupold wrote DNN does currently not support DST, users and  admins need to adjust timezone settings.

Hi Sebastian,

do you mean we should change timezone when we're in DST? As far as I can see, the problem affects the CurrentDate skinobject only, not any datetime inside DNN. At least, I get the right time in a control of mine, where I get it with this code:

txtCreatedDate.Text = formatDateTime(DateTime.Now, Dateformat.ShortDate) & " " & formatDateTime(DateTime.Now, Dateformat.ShortTime)

Currentdate does:

 Dim objUserTime As New UserTime
If Dateformat <> "" Then
    lblDate.Text = format(objUserTime.CurrentUserTime, Dateformat)
Else
    lblDate.Text = objUserTime.CurrentUserTime.ToLongDateString
End If

I'm investigating how UserTime is handled. Of course my code does not take into consideration user timezone, which is - I believe - causing the problem.