[GH-ISSUE #283] Events disappear in Outlook after sync with Horde #276

New issue

Closed

opened 2026-02-25 20:31:18 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 20:31:18 +03:00

Owner

Originally created by @mytickets617 on GitHub (Aug 11, 2020).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/283

After sync:

No events, old and new, from Horde appear in Outlook.
All event, old and new, from Outlook appear in Horde and disappear in Outlook.

Same issue with log/reports/config and detailed description is reported here:
https://sourceforge.net/p/outlookcaldavsynchronizer/tickets/1431/

Originally created by @mytickets617 on GitHub (Aug 11, 2020). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/283 After sync: 1) No events, old and new, from Horde appear in Outlook. 2) All event, old and new, from Outlook appear in Horde and disappear in Outlook. Same issue with log/reports/config and detailed description is reported here: https://sourceforge.net/p/outlookcaldavsynchronizer/tickets/1431/

kerem closed this issue

2026-02-25 20:31:18 +03:00

kerem commented

2026-02-25 20:31:19 +03:00

Author

Owner

@amulet1 commented on GitHub (Aug 14, 2020):

It appears to be entirely a problem on Horde's end.

Here is what was done to fix the issue:

Increased memory limit in php.ini to 256M:
memory_limit = 256M

Apparently some operations related to CalDav may require way more than 128M of memory for PHP process.

Performed the following updates in horde database:

UPDATE kronolith_events SET event_baseid="" WHERE event_baseid IS NULL;
ALTER TABLE kronolith_events MODIFY event_baseid varchar(255) NOT NULL DEFAULT "";

Everywhere is the code the assumption is that event_baseid can not be null. Additionally, when the event_baseid field was added (via migration), it was supposed to have empty string as default value, but in our case for whatever reason its default was set to NULL. We also added NOT NULL constraint there, just in case.

Without this change some events (specificaly events that were created by Outlook CalDav synchronizer were assigned NULL event_baseid and were never retrieved when synchronizing with Outlook using CalDavSynchronizer. This caused their disappearance in Outlook.

Replaced horde/kronolith/lib/Kronolith.php with the modified version with 2 specific fixes (we can provide a patch):
One is to address exception happening when startDate is not set in addEvents() call.
The other is to added issue with empty list of events generated if the end date was not specified.

With these fixes the synchronization now works properly. And also it is now possible to open calendars via horde/rpc.php, browse individual events, etc.

@amulet1 commented on GitHub (Aug 14, 2020): It appears to be entirely a problem on Horde's end. Here is what was done to fix the issue: 1. Increased memory limit in php.ini to 256M: memory_limit = 256M Apparently some operations related to CalDav may require way more than 128M of memory for PHP process. 2. Performed the following updates in horde database: UPDATE kronolith_events SET event_baseid="" WHERE event_baseid IS NULL; ALTER TABLE kronolith_events MODIFY event_baseid varchar(255) NOT NULL DEFAULT ""; Everywhere is the code the assumption is that event_baseid can not be null. Additionally, when the event_baseid field was added (via migration), it was supposed to have empty string as default value, but in our case for whatever reason its default was set to NULL. We also added NOT NULL constraint there, just in case. Without this change some events (specificaly events that were created by Outlook CalDav synchronizer were assigned NULL event_baseid and were never retrieved when synchronizing with Outlook using CalDavSynchronizer. This caused their disappearance in Outlook. 3. Replaced horde/kronolith/lib/Kronolith.php with the modified version with 2 specific fixes (we can provide a patch): One is to address exception happening when startDate is not set in addEvents() call. The other is to added issue with empty list of events generated if the end date was not specified. With these fixes the synchronization now works properly. And also it is now possible to open calendars via horde/rpc.php, browse individual events, etc.

kerem referenced this issue

2026-03-01 17:41:14 +03:00

[GH-ISSUE #276] Sync Failure with recurring appointment #735

kerem referenced this issue

2026-03-14 00:31:36 +03:00

[GH-ISSUE #276] Sync Failure with recurring appointment #1169