* easy: => 0
* stage: Design decision needed => Fixed on a branch
Comment:
Replying to [comment:3 russellm]:
> Ultimately, I suspect that this will end up being fixed as a result of
addressing #2626.
Indeed, this is fixed in the timezone support branch -- see "Multiple
timezone support for datetime representation" thread on django-developers.
--
Ticket URL: <https://code.djangoproject.com/ticket/14253#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => fixed
Comment:
I think we can consider this fixed at r17106, which addressed #2626.
--
Ticket URL: <https://code.djangoproject.com/ticket/14253#comment:11>
Comment (by aaugustin):
In fact, time zone support isn't sufficient, because most sites won't have
per-user time zones: it's a lot of work just to fix the "now" button in
the admin. We still need the cosmetic fix in addition to the systemic fix.
(That wasn't obvious at first; we did things in the right order.)
There's a new attempt to fix this in #20663.
--
Ticket URL: <https://code.djangoproject.com/ticket/14253#comment:12>
Comment (by Aymeric Augustin <aymeric.augustin@…>):
In [changeset:"7e6d852bac4de2d5ed2d5ddeabf71482d644ef51"]:
{{{
#!CommitTicketReference repository=""
revision="7e6d852bac4de2d5ed2d5ddeabf71482d644ef51"
Fixed #20663 -- "Today" and "now" admin shortcuts.
Changed the shortcuts next to date and time intput widgets
to account for the current timezone.
Refs #7717, #14253 and #18768.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/14253#comment:13>