diff options
| author | Lucas Perais (lpe) <lpe@odoo.com> | 2018-10-18 13:48:36 +0000 |
|---|---|---|
| committer | Lucas Perais (lpe) <lpe@odoo.com> | 2018-10-23 11:26:28 +0000 |
| commit | eef4c3b48bcb4feac028bf640b545006dd0c9b91 (patch) | |
| tree | e2b7fc81627dac8a54df236751f28ac75244b5b6 /doc/_extensions | |
| parent | 5dea3651f133b1096fede9ee476cf5dfcc255f28 (diff) | |
[FIX] calendar: all day event shouldn't store in UTC
With a user in a distant timezone, like UTC +/- 11
Create a all day event.
Before this commit, the event was displayed across the wrong days
This was because the dates were converted from the user's timezone
into UTC before being stored.
Which is:
- start date at december, 12
- if the user's tz is utc-11: the date becomes december, 11 (at 1:00pm)
- at rendering, it becomes december, 11 (at 7:00am)
After this commit, we store the datetime field "as if" it were a date field
that is, we don't convert it to any particular tz
It is worth noting that, if one removes the allday mapping in the xml view,
an event that has been created as allday will get its start and stop date converted
to the browser's timezone, and will NOT be displayed as from 8am to 8pm as one could expect
This is considered as a limitation of the code, that was present before this commit anyway.
In any case, please do not revert this commit :D
OPW 1891110
closes odoo/odoo#27949
Diffstat (limited to 'doc/_extensions')
0 files changed, 0 insertions, 0 deletions
