Read the statement by Michael Teeuw here.
Weekly recurring calendar events off by 1 day
-
I have two recurring events on a Wednesday, one at 6.00pm PST and another at 6.10pm PST. These appear in the calendar on Thursday, instead of Wednesday. I’m using MMM-CalExt3Agenda, but this also happens in the default Calendar module.
When these events are set to occur “weekly on Wednesday” they appear on Thursday, and when they are set to occur “every 7 days”, they do not appear at all.
I’ve done a lot of research into this issue, and most recently tried looking at the fixes used in #2905 (stemming from this post here), but I’m still having this issue. I’m on top of tree master branch (6e80e5a2952b4e4b849c31a05982b8a9a0157ecd) , but have also tried the latest develop branch.
Below are two VEVENT tests that replicate this issue.
This one is set for weekly on Thursday and does not appear at all
BEGIN:VEVENT DTSTART;TZID=America/Los_Angeles:20230112T181000 DTEND;TZID=America/Los_Angeles:20230112T201000 RRULE:FREQ=WEEKLY;BYDAY=TH DTSTAMP:20230111T185748Z UID:5ou9pn86ni4po343lvomeaud1k@google.com CREATED:20230111T184240Z DESCRIPTION: LAST-MODIFIED:20230111T185200Z LOCATION: SEQUENCE:3 STATUS:CONFIRMED SUMMARY:Test Event Weekly TRANSP:OPAQUE END:VEVENTThis one is set for every 7 days and appears a day late
BEGIN:VEVENT DTSTART;TZID=America/Los_Angeles:20230112T180000 DTEND;TZID=America/Los_Angeles:20230112T200000 RRULE:FREQ=DAILY;INTERVAL=7 DTSTAMP:20230111T185748Z UID:7birsokpqt7dnq3kpbdndsaud2@google.com CREATED:20230111T184307Z DESCRIPTION: LAST-MODIFIED:20230111T185049Z LOCATION: SEQUENCE:4 STATUS:CONFIRMED SUMMARY:Test Event Every 7 Days TRANSP:OPAQUE END:VEVENT@sdetweil this one was your fix, do you have any additional insight into this for me please?
-
@akriegshauser I will have to test, but pretty sure its the rrule processing returning a different date when this condition is set
2905 only checks for
(curEvent.rrule.origOptions.byweekday !== undefined) {
-
@sdetweil , yeh , I see the error
on the weekly the rrule returned
“2023-01-19T02:10:00.000Z”
for the 1st date. but technically this is wrong… should have been -01-20:02:10 z as its UTC time… past midnight on the 20th in England … -8 to LA, to 1800 on the 19, but it has 19… to LA time 18th
this is what I see
so rrule is broken still … i’ll look at it to see if there is a fix… may not get to it before the weekend
-
@sdetweil Thanks for looking into this, I appreciate it!
-
@sdetweil Hi Sam, just checking in to see if you may have made any progress on this one?
-
@akriegshauser sorry, not yet.
I will be traveling for the next week, and don’t know what kind of time I’ll have after that yet.
this a particularly difficult one, as we don’t know what the recurring date is SUPPOSED to be, thats RRULE’s job
-
@sdetweil Have you been able to find any time to look into this? I’m still seeing quite frequent occurrences of these issues.
-
@akriegshauser no sorry, been swamped with other stuff
