IcalXML.php Error – 300 lines of errors and growing

Is it possible to disable iCal Creator from this plugin? I would gladly lose iCal functionality if it might my erro log would not grow exponentially each day.

v2.29.21 was released in January, so presumably it’s just a matter of incorporating that update.

https://github.com/iCalcreator/iCalcreator/

Also, how it is included in this project is prone to cause problems – the package namespace should be prefixed so other plugins can also use the same packages.

https://github.com/coenjacobs/mozart

Thanks Brian. I hope someone from All In One is actually reading this. Thanks

It appears that Timely has abandoned updates on their plugin. When I sent a message to report the errors, they suggest using their paid subscription service instead.

I have stopped the error log generation by making the following changes to lines 318 and 718 in the file IcalXML.php

Line 318 change from:
@is_null( $content[Util::$LCparams][Util::$TZID] )) {

Line 318 change to:
(isset($TZID) && @is_null( $content[Util::$LCparams][Util::$TZID] )) ) { // added isset to stop errorlog

Line 718 change from:
( Util::$MINUS != $content[0] ) &&

Line 718 change to:
(isset($content[0]) && ( Util::$MINUS != $content[0] )) && // added isset to stop errorlog

Thanks but too little , too late. I given up on Time.ly based on lack of support one both the free (and from what I read) as well as paid version fo their product. I have since moved my entire calendar to the much better supported product of https://www.ads-software.com/plugins/modern-events-calendar-lite/

Good find @omarkoza!

Unfortunately I have the Time.ly ai1ec plugin deeply integrated with my own plugin and would have substantial recoding to integrate another calendar plugin. I have fixed their issues as I find them so it continues to work with my application.

Hi Rhapsody – yeah it was not a decision I took lightly. I tried very hard to work with Time.ly to resolve this issue but they have chosen to all but to ignore my request (as well as those of many many others) But I do appreciate the code edit. Good to know!

Seems the plugin was updated without updating this library!