Skip to content
This repository has been archived by the owner on Jun 10, 2020. It is now read-only.

Problems with recurring events showing for days when they have been removed #83

Open
emlowe opened this issue Apr 8, 2020 · 2 comments

Comments

@emlowe
Copy link

emlowe commented Apr 8, 2020

Love your extension BTW.
Google calendar using private ICAL link (ICS).

I have several recurring events that happen weekly. However, if during some week, you decide to remove that event for the week, it doesn't seem to propagate correctly.

I'm not sure if this is the EXDATE not working properly or not. For example, the following event shows up:

BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20191203T180000
DTEND;TZID=America/Los_Angeles:20191203T190000
DTSTAMP:20200408T000157Z
UID:DCF3A5A6-E936-4F86-95F4-A68891CF9F4A
RECURRENCE-ID;TZID=America/Los_Angeles:20191203T180000
CREATED:20190704T053758Z
DESCRIPTION:Mr. XXX
LAST-MODIFIED:20200407T235514Z
LOCATION:Studio E
SEQUENCE:28
STATUS:CONFIRMED
SUMMARY:L—Hip Hop Tech @ 6-7pm
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20190820T180000
DTEND;TZID=America/Los_Angeles:20190820T190000
EXDATE;TZID=America/Los_Angeles:20191029T180000
EXDATE;TZID=America/Los_Angeles:20191112T180000
EXDATE;TZID=America/Los_Angeles:20191119T180000
EXDATE;TZID=America/Los_Angeles:20191126T180000
EXDATE;TZID=America/Los_Angeles:20191224T180000
EXDATE;TZID=America/Los_Angeles:20191231T180000
EXDATE;TZID=America/Los_Angeles:20200317T180000
EXDATE;TZID=America/Los_Angeles:20200324T180000
EXDATE;TZID=America/Los_Angeles:20200331T180000
EXDATE;TZID=America/Los_Angeles:20200407T180000
EXDATE;TZID=America/Los_Angeles:20200414T180000
RRULE:FREQ=WEEKLY;UNTIL=20200617T010000Z
DTSTAMP:20200408T000157Z
UID:DCF3A5A6-E936-4F86-95F4-A68891CF9F4A
CREATED:20190704T053758Z
DESCRIPTION:Mr. XXX
LAST-MODIFIED:20200407T235514Z
LOCATION:Studio E
SEQUENCE:28
STATUS:CONFIRMED
SUMMARY:L—Hip Hop Tech @ 6-7pm
TRANSP:OPAQUE
X-BUSYMAC-LASTMODBY:XXXXXX
END:VEVENT

But it does not in Google Calendar.

@eouia
Copy link
Owner

eouia commented Apr 8, 2020

This module is using old 3rd party parser(originally same root with default calendar module), but it has several bugs on certain conditions.
If possible, try MMM-CalendarExt2, it is newer and more powerful.

@emlowe
Copy link
Author

emlowe commented Apr 8, 2020

I have tried MMM-CalendarExt2 - but most of the time it doesn't render anything in the browser. I am using the default everything, and I get nothing in the browser (testing with node serveronly).

I see logs:

[CALEXT2] calendar:0 >> Scanning start with interval:1800000
[CALEXT2] calendar:0 >> Scanned: 1053, Selected: 1053

There are no errors in the browser log. I am using the following config

{
    module: "MMM-CalendarExt2",
    config: {
        calendars: [
          {
            url: <private google url>,
          },
        ],
        views: [
          {
            mode: "daily",
           },
        ],
        scenes: [
          {
            name: "DEFAULT",
          },
        ],
     }
},

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants