1 Topic by Jacques

  • Jacques
  • Guest

Topic: Problem with export ICS

Sorry for my english, french version below...
Luxcal v5.3.3M
If I export (via crontab ou action) my calendar in ics file, all are OK except if I have an event with repetition and exception of this.
So, if an event begin to one day, is every week the same day and I have deleted 2 ou 3 entries in this serie, the exported event contain the DayStart, the DayEnd and the rule of the repetition but non exception.
And if I import this in another calendar, the event start at the DayStart, end at the DayEnd and is repeated every week...
Luxcal is a very good calendar and I have mad some modifications in the presentation in my web site, so I don't test in 5.3.4 version. But nothing in the announcement is about ICS export.
Thank you for your help or a correction of this problem.
Jacques

Si j'exporte via la CRO tab ou l'interface mon calendrier dans un fichier ics, tout est OK sauf si un j'ai un évènement avec des répétitions et des exceptions dans celles-ci.
Si j'ai un évènement qui débute un jour, se répète toutes les semaines le même jour et que j'ai supprimé 2 ou 3 entrées dans cette série, l'événement exporté contiendra le jour de début, le jour de fin, les règles de répétition mais pas les exceptions.
Et si j'importe cet événement dans un autre calendrier, il débutera au 1er jour, finira au dernier et se répétera toutes les semaines...
Luxcal est un excellent calendrier et j'ai fait quelques modifications dans sa présentation sur mon site web, donc je n'ai pas testé la version 5.3.4. Mais rien dans son annonce ne concerne l'export ICS.
Merci pour votre aide ou la correction de ce problème.

Quote Post 1

2 Reply by Jacques

  • Jacques
  • Guest

Re: Problem with export ICS

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

Quote Post 2

3 Reply by Jacques

  • Jacques
  • Guest

Re: Problem with export ICS

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.

Quote Post 3

  • Roel
  • Roel
  • Administrator
  • Offline
  • Registered: 2018-02-26
  • Posts: 602

Re: Problem with export ICS

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

Quote Post 4

5 Reply by Jacques

  • Jacques
  • Guest

Re: Problem with export ICS

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

Quote Post 5

6 Reply by Jacques

  • Jacques
  • Guest

Re: Problem with export ICS

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";
    }                   
}

Quote Post 6

7 Reply by Jacques

  • Jacques
  • Guest

Re: Problem with export ICS

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

Quote Post 7

  • Roel
  • Roel
  • Administrator
  • Offline
  • Registered: 2018-02-26
  • Posts: 602

Re: Problem with export ICS

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

Quote Post 8

9 Reply by Jacques

  • Jacques
  • Guest

Re: Problem with export ICS

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

Quote Post 9

  • Roel
  • Roel
  • Administrator
  • Offline
  • Registered: 2018-02-26
  • Posts: 602

Re: Problem with export ICS

Hi Jacques,
I've changed the toolbox.js file exactly as you suggest in your post above. So this change will be part of the next LuxCal calendar version.
Roel

Quote Post 10