You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The time is correctly displayed by RRULE as (9am): Wed Oct 21 2020 09:00:00 GMT+0200 (South Africa Standard Time)
What does the calendar show
When i specify the RRULE string on the fullcalendar object exactly as above displays it 7am. This is UTC and not the timezone of the calendar.
It seems that it is interpreting RRULEs as if the calendar were in UTC mode and not using the timezone.
The text was updated successfully, but these errors were encountered:
ganySA
changed the title
RRULE DTSTART Ignores timezone setting on calendar and assumes UTC.
RRULE DTSTART Ignores timezone setting on calendar and assumes UTC + testcase
Oct 24, 2020
I believe this existing ticket captures this need: #5273
↑
Please visit the above issue, give a 👍 to vote (?), press the 🔈Subscribe button to receive updates.
Reduced Test Case
Test Case
https://codesandbox.io/s/fullcalendar-z-char-issue-forked-06fw0?file=/src/RRuleDemo.js
Bug Description
When interpreting DTSTART it ignores timezone setting on calendar and seems to interpret as UTC.
Background
Database: time saved as UTC.
Fullcalendar: timezone specified as per a database value in my case 'Africa/Johannesburg'.
Luxon library used.
The data in my database is UTC and this works perfectly for normal events the calendar converts them correctly to the correct timezone.
What does RRULE show
Below is my RRULE (7am in UTC)
FREQ=DAILY;INTERVAL=1;DTSTART=20201021T070000Z
When i take the above and use RRULE as follows:
The time is correctly displayed by RRULE as (9am):
Wed Oct 21 2020 09:00:00 GMT+0200 (South Africa Standard Time)
What does the calendar show
When i specify the RRULE string on the fullcalendar object exactly as above displays it 7am. This is UTC and not the timezone of the calendar.
It seems that it is interpreting RRULEs as if the calendar were in UTC mode and not using the timezone.
The text was updated successfully, but these errors were encountered: