-
Notifications
You must be signed in to change notification settings - Fork 23.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Messy timezone mangling in website_event #27179
Comments
yajo
added a commit
to Tecnativa/event
that referenced
this issue
Sep 24, 2018
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
Tardo
pushed a commit
to Tecnativa/event
that referenced
this issue
May 13, 2019
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
ajaniszewska-dev
pushed a commit
to ajaniszewska-dev/event
that referenced
this issue
Sep 28, 2020
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
ajaniszewska-dev
pushed a commit
to ajaniszewska-dev/event
that referenced
this issue
Sep 29, 2020
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
damdam-s
pushed a commit
to damdam-s/event
that referenced
this issue
Jun 10, 2021
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
damdam-s
pushed a commit
to damdam-s/event
that referenced
this issue
Jun 10, 2021
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
chandni299
pushed a commit
to elego/event
that referenced
this issue
Nov 15, 2021
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
chandni299
pushed a commit
to elego/event
that referenced
this issue
Dec 14, 2021
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
Camille0907
pushed a commit
to Camille0907/event
that referenced
this issue
Dec 16, 2022
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
Dear @yajo, Thank you for your report but we are closing it due to inactivity. This is an automated message. |
Camille0907
pushed a commit
to Camille0907/event
that referenced
this issue
Jun 7, 2023
Before this patch, the user was getting the Public User's TZ on the calendar view. After merged, only the event's timzeone will be used to display dates. It is, however, affected by odoo/odoo#27179, which means that there is a possible mismatch between the date used to search and the one used to display, most likely to be hit when events have very different timzeones. Added to Known Issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Impacted versions: 9-12
Steps to reproduce:
Today it's September 24th, 2018. This is the calendar for this week and the next one:
I'm Administrator, I live in Madrid:
I schedule an event in Sydney. It should be on October 1st, 2018, from 6 AM to 8 AM. I'm smart enough to compute mentally the tzdiff between Madrid and Sydney and I end up with this:
I publish the event in the website.
I log out.
I go to the website and check events for this week:
Current behavior:
Expected behavior:
@Tecnativa
The text was updated successfully, but these errors were encountered: