Post new reply

Thanks Roel,

OK for testing this files. I send you my mail this morning.
I suggest you to also manage importing ICS file with many EXDATE attributs, to convert in the syntax used in xDates field in the database...
And a very small evolution in toolbox.js in the OpenWin() function (line 141 for me) :
replace : const evtWinL = (screen.width - evtWinW) / 2;
with : const evtWinL = screen.left + ((screen.width - evtWinW) / 2);
If you are many screens, the popup is open now in the same screen of Luxcal application.

Thanks,
Jacques

Hi Jacques,
Thank you for your very clear description of the 3 problems.
I have fixed all three problems in both files exportIcs.php and expical.php. I would be grateful if you could also test these files, so that we are sure all works fine.
If you are willing to do this, could you please send me your email address (via the Contact page). I will then send you the changed files.
Roel

I don't know if it's mandatory, but the Timezone information isn't included in the ICS export.
If it needs to be included, the VTIMEZONE block, including the DAYLIGHT and STANDARD blocks if necessary, must be placed between the last END:VEVENT and the END:VCALENDAR line.

END:VEVENT
BEGIN:VTIMEZONE
TZID:Europe/Paris
BEGIN:DAYLIGHT
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
END:VCALENDAR

Jacques

So, the correction in the explical.php it's OK with :
if ($evt['mdt']) {
    if ($evt['mdt'] == "9999-00-00 00:00") {
        $icsBody .= "LAST-MODIFIED:".gmdate('Ymd\THis\Z',strtotime($evt['adt']))."\r\n";
    } else {
        $icsBody .= "LAST-MODIFIED:".gmdate('Ymd\THis\Z',strtotime($evt['mdt']))."\r\n";
    }                   
}

Thanks Roel,

I continue to test export ICS and I have another anormal thing :
- in the table mycal_events, the fields aDateTime = "2026-01-27 15:33" and mDateTime = "9999-00-00 00:00"
- in the ICS export, the attributs are : CREATED:20260127T143300Z and LAST-MODIFIED:99981129T230000Z
The CREATED attribut is OK with the timezone
The LAST-MODIFIED is very strange !!! and if I compare this value with the value indicated by another calendar after modification, the last date can not be the good.
So, I suggest you replace the mDateTime for the export with aDateTime if the value is the default value.

It's finally 3 problems:
- exclude dates (it' ok for import with EXDATE)
- uid with space (it' ok with a '_')
- last-modified whith default value

Jacques

Hello Jacques,
Thank you for reporting these two problems. I will look into the problems and try to fix them as soon as possible.
After having looked into the problems and hopefully solved them, I will be back here.
Roel

Another problem with export in ICS file, if the title of the event contain a space, the UID (based on this title) contain also a space.
If I import this ICS file into a calendar, this UID is refused.
So, replace space witch '_' close the problem.

Regarding ICS export: It appears possible to exclude dates from an event using the EXDATE field.