#21074 closed Bug (fixed)
DateTimeField: Using localized_fields breaks timezone conversion
Reported by: | Matt Austin | Owned by: | Aymeric Augustin |
---|---|---|---|
Component: | Forms | Version: | 1.6-beta-1 |
Severity: | Release blocker | Keywords: | timezone localization forms |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
If I add a DateTimeField to the form's localized_fields
Meta property (in order to get the date correctly formatted), then the rendered field value is no longer converted to the activated timezone. This also occurs when setting localized=True
on the DateTimeField.
Using Django 1.6b2.
Change History (8)
comment:1 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Triage Stage: | Unreviewed → Accepted |
Type: | Uncategorized → Bug |
comment:2 by , 11 years ago
Owner: | removed |
---|---|
Severity: | Normal → Release blocker |
Status: | assigned → new |
There's a good reason why I didn't know about localized_fields
: they're a new feature in 1.6.
The corresponding ticket is #13546 and the commit is [756b81db].
Since it's a major bug in a new feature, I'm marking the ticket as a release blocker.
Since it isn't a bug in my code, I'm deassigning myself.
comment:3 by , 11 years ago
Owner: | set to |
---|---|
Severity: | Release blocker → Normal |
Status: | new → assigned |
Florian rightfully points out that, if the bug can be triggered by setting localize=True
on a DateTimeField
, it isn't new in 1.6. I'll have to deal with it.
comment:4 by , 11 years ago
Severity: | Normal → Release blocker |
---|
Phew, it's actually a regression in 1.6 introduced in [893d8de6] which fixed #18777.
Florian and I independently identified this commit through bisection.
comment:7 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I wasn't aware of
localized_fields
. I'll look into it.