In Javascript it prints:
{{{
> new Date()
Tue Jun 28 2022 00:25:07 GMT+0200 (South Africa Standard Time)
}}}
On the linux server running Django (a different computer to my browser):
{{{
$ date
Tue 28 Jun 2022 12:25:48 AM SAST
}}}
But in the Django admin if I click the now of a date/time widget it adds:
{{
2022-06-27 17:26:23
Note: You are 7 hours ahead of server time.
}}}
It says I am 7 hours ahead, but my computer is set to SAST as well.
This is my timezone settings (using Django==4.0.1, with zoneinfo):
{{{
# SAST = South African Standard Time is GMT+2
USE_TZ = True
TIME_ZONE = 'Africa/Johannesburg'
}}}
I see there was work on this issue about a decade ago. Not sure where the
wonky "now" time is coming from.
--
Ticket URL: <https://code.djangoproject.com/ticket/33810>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Old description:
> The current time where I am is 00:25
>
> In Javascript it prints:
> {{{
> > new Date()
> Tue Jun 28 2022 00:25:07 GMT+0200 (South Africa Standard Time)
> }}}
>
> On the linux server running Django (a different computer to my browser):
> {{{
> $ date
> Tue 28 Jun 2022 12:25:48 AM SAST
> }}}
>
> But in the Django admin if I click the now of a date/time widget it adds:
> {{
> 2022-06-27 17:26:23
> Note: You are 7 hours ahead of server time.
> }}}
> It says I am 7 hours ahead, but my computer is set to SAST as well.
>
> This is my timezone settings (using Django==4.0.1, with zoneinfo):
> {{{
> # SAST = South African Standard Time is GMT+2
> USE_TZ = True
> TIME_ZONE = 'Africa/Johannesburg'
> }}}
>
> I see there was work on this issue about a decade ago. Not sure where the
> wonky "now" time is coming from.
New description:
The current time where I am is 00:25
In Javascript it prints:
{{{
> new Date()
Tue Jun 28 2022 00:25:07 GMT+0200 (South Africa Standard Time)
}}}
On the linux server running Django (a different computer to my browser):
{{{
$ date
Tue 28 Jun 2022 12:25:48 AM SAST
}}}
But in the Django admin if I click the now of a date/time widget it adds:
{{{
2022-06-27 17:26:23
Note: You are 7 hours ahead of server time.
}}}
It says I am 7 hours ahead, but my computer is set to SAST as well.
This is my timezone settings (using Django==4.0.1, with zoneinfo):
{{{
# SAST = South African Standard Time is GMT+2
USE_TZ = True
TIME_ZONE = 'Africa/Johannesburg'
}}}
I see there was work on this issue about a decade ago. Not sure where the
wonky "now" time is coming from.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/33810#comment:1>
* status: new => closed
* type: Uncategorized => Bug
* resolution: => needsinfo
Comment:
The admin's site operates in the server time and it works for me with
`TIME_ZONE = 'Africa/Johannesburg'`. I don't think you've explained the
issue in enough detail to confirm a bug in Django. Please reopen the
ticket if you can debug your issue and provide details about why and where
Django is at fault. If you're having trouble understanding how Django
works, see TicketClosingReasons/UseSupportChannels for ways to get help.
--
Ticket URL: <https://code.djangoproject.com/ticket/33810#comment:2>
Comment (by Michael):
Replying to [comment:2 Mariusz Felisiak]:
> The admin's site operates in the server time and it works for me with
`TIME_ZONE = 'Africa/Johannesburg'`. I don't think you've explained the
issue in enough detail to confirm a bug in Django. Please reopen the
ticket if you can debug your issue and provide details about why and where
Django is at fault. If you're having trouble understanding how Django
works, see TicketClosingReasons/UseSupportChannels for ways to get help.
As explained and checked the server time is SAST, and Django settings is
set to SAST, and so is my computer SAST, but Django Admin is showing a 7hr
timezone error. I am not asking for help, there is nothing else one can
change, the admin site is auto generated.
--
Ticket URL: <https://code.djangoproject.com/ticket/33810#comment:3>