Opened 6 years ago
Last modified 5 years ago
#29724 closed Bug
Admin date_hierarchy filter by month displays an extra day — at Version 4
Reported by: | Lavrenov Ivan | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | yes |
Description (last modified by )
When I authorized by user with not-UTC timezone, like America/Los_Angeles , and open filter by date in month, I see one extra day, that follows to the first day of the previous month
Change History (5)
by , 6 years ago
Attachment: | Снимок экрана 2018-08-29 в 16.59.28.png added |
---|
follow-up: 3 comment:1 by , 6 years ago
Summary: | Bug with time filter in django admin → Admin date_hierarchy filter by month displays an extra day |
---|
Could you be more specific about how to reproduce this? I thought you meant TIME_ZONE = 'Los-Angeles/America'
but I get "Incorrect timezone setting". Which database are you using?
comment:2 by , 6 years ago
The timezone is America/Los_Angeles, sorry for inaccuracy.
I'm using Mysql database. I think it is something сonnected with converstion to local time. I have a record, which in UTC in the 1st September, but in local time it is still in the 31 August.
P.S. Values stored in UTC format
comment:3 by , 6 years ago
Replying to Tim Graham:
Could you be more specific about how to reproduce this? I thought you meant
TIME_ZONE = 'Los-Angeles/America'
but I get "Incorrect timezone setting". Which database are you using?
The timezone is America/Los_Angeles, sorry for inaccuracy.
I'm using Mysql database. I think it is something сonnected with converstion to local time. I have a record, which in UTC in the 1st September, but in local time it is still in the 31 August.
P.S. Values stored in UTC format
comment:4 by , 6 years ago
Description: | modified (diff) |
---|
representation of bug