ics_calendar icon indicating copy to clipboard operation
ics_calendar copied to clipboard

include_all_day not seems to work

Open jflefebvre06 opened this issue 1 year ago • 2 comments

Hello,

I try to integrate with the following config (french School vacation)

ics_calendar:
  calendars:
    - name: "Vacances scolaires 2"
      url: "https://fr.ftp.opendatasoft.com/openscol/fr-en-calendrier-scolaire/Zone-B.ics"
      include_all_day: True

image

All day not seems to work

jflefebvre06 avatar Nov 23 '23 11:11 jflefebvre06

I notice this issue with multi-day all-day events. I'm pulling ICS calendars from two different O365 instances. Neither seem to respect the default include_all_day behavior as it relates to multi-day all-day events and the events are included on the calendar.

I was able to remove the multi-day all-day events by changing the parser to ics, but that created an offset issue that I fixed with offset_hours, However, this will need to be managed w/ daylight savings.

This event was not included with the default RIE parser. BEGIN:VEVENT UID: SUMMARY:DND Day DTSTART;VALUE=DATE:20230703 DTEND;VALUE=DATE:20230704 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20231205T221637Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION: X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-BUSYSTATUS:WORKINGELSEWHERE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:TRUE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 X-MICROSOFT-DONOTFORWARDMEETING:FALSE X-MICROSOFT-DISALLOW-COUNTER:FALSE X-MICROSOFT-REQUESTEDATTENDANCEMODE:DEFAULT END:VEVENT

This event remains on the calendar using the RIE parser. BEGIN:VEVENT UID: SUMMARY:SPIRIT - Remote Revisit DTSTART;VALUE=DATE:20231204 DTEND;VALUE=DATE:20231209 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20231205T221637Z TRANSP:TRANSPARENT STATUS:CONFIRMED SEQUENCE:0 LOCATION: X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-BUSYSTATUS:FREE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:TRUE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 X-MICROSOFT-DONOTFORWARDMEETING:FALSE X-MICROSOFT-DISALLOW-COUNTER:FALSE X-MICROSOFT-REQUESTEDATTENDANCEMODE:DEFAULT END:VEVENT

Is there anything else I can provide to help diagnose this? Or is there another workaround I may be missing?

jstuhlsatz avatar Dec 05 '23 23:12 jstuhlsatz

Thanks very much for the info. I’ll try to get to this next week, but no guarantees, this is a busy time of year for me. On Dec 5, 2023, at 6:47 PM, jstuhlsatz @.***> wrote: I notice this issue with multi-day all-day events. I'm pulling ICS calendars from two different O365 instances. Neither seem to respect the default include_all_day behavior as it relates to multi-day all-day events and the events are included on the calendar. I was able to remove the multi-day all-day events by changing the parser to ics, but that created an offset issue that I fixed with offset_hours, However, this will need to be managed w/ daylight savings. This event was not included with the default RIE parser. BEGIN:VEVENT UID: SUMMARY:DND Day DTSTART;VALUE=DATE:20230703 DTEND;VALUE=DATE:20230704 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20231205T221637Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION: X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-BUSYSTATUS:WORKINGELSEWHERE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:TRUE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 X-MICROSOFT-DONOTFORWARDMEETING:FALSE X-MICROSOFT-DISALLOW-COUNTER:FALSE X-MICROSOFT-REQUESTEDATTENDANCEMODE:DEFAULT END:VEVENT This event remains on the calendar using the RIE parser. BEGIN:VEVENT UID: SUMMARY:SPIRIT - Remote Revisit DTSTART;VALUE=DATE:20231204 DTEND;VALUE=DATE:20231209 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20231205T221637Z TRANSP:TRANSPARENT STATUS:CONFIRMED SEQUENCE:0 LOCATION: X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-BUSYSTATUS:FREE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:TRUE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 X-MICROSOFT-DONOTFORWARDMEETING:FALSE X-MICROSOFT-DISALLOW-COUNTER:FALSE X-MICROSOFT-REQUESTEDATTENDANCEMODE:DEFAULT END:VEVENT` Is there anything else I can provide to help diagnose this? Or is there another workaround I may be missing?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

franc6 avatar Dec 06 '23 00:12 franc6