diff options
| author | Nicolas Lempereur <nle@odoo.com> | 2018-01-22 12:04:27 +0100 |
|---|---|---|
| committer | Nicolas Lempereur <nle@odoo.com> | 2018-01-22 12:38:52 +0100 |
| commit | 7a63d471edec45a106fef5f783aeb7eaf43447f6 (patch) | |
| tree | e54183e6ba7a25c6bf40f97182b6c904ce6fbb35 /addons/web/static/src/js/views/basic/basic_model.js | |
| parent | aac9cd4ca8080335ab794098c04d007ca3fb2461 (diff) | |
[FIX] website_event_track: use event timezone
Depending on the location, on the website different timezone were used
to display tracks:
- in `Agenda` day date (as of saas-14): the current user timezone
- in `Agenda` track times: the event timezone
- in `Talks` subtitle: the event timezone
- in `Talks` tracks: the current user timezone
- in a track page: the first user (admin) timezone
With this change in all those instance the event timezone is used.
There is still a usability hindrance in the backend: the timezone used
when encoding track or event datetime is the browser timezone.
So if the browser is GMT+2 and the event is GMT+6, encoding a 4h00 time
would save it as 2h00 (in UTC) and display it on the website as 8h00.
This would make sense to encode these datetime in user timezone but
currently there is no framework option to do it.
opw-805358
closes #22427
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_model.js')
0 files changed, 0 insertions, 0 deletions
