Tickets :: Comment on [#13449] CalDAV / CardDAV sync need multiple logins / session to work

* Your Email Address
* Spam protection	Enter the letters below: . .. .__..__ . , \|\/\|\| [__][ __ \./ \| \|\|___\| \|[_./ \|
Comment	>> Does this still happen with the latest version of all packages? There >> had been a related fix with sessions and RPC access recently. > > I upgraded all packages on two of my customers installations to check > whether iCAL4OL fails or succeeds against Horde 5.2.3. > > I first created a clean configuration ini file for iCAL4OL to rule > out any changes I might have done over time. iCAL4OL then auto > detected the calendars from one user and wrote the settings to the > ini file. No trouble so far, but I think iCAL4OL also detected that I > want so sync against Horde and automatically added a "horde" tag to > it's configuration to counter the session/login error. > I manually removed that tag to see if a sync would succeed and as far > as I can tell it did that without complaining. All calendar entries > are in sync. I tried it both ways and then with multiple calendars > and it still works. > > I would like to have Roland check it against the Horde demo server to > see if my observations are true. > > Regarding the Lightning/TB failure: I do have a customer who started > to use CalDAV sync with Lightning last week. Synching only one > calendar seems to work fine, but using more than one calendar seems > to break things. It won't sync at all after a restart of TB, giving > me a CALDAV_ERROR and a can't read data message. I don't think that > this is related to the session/Login bug, but I can try to > investigate.
Attachment
Watch this ticket

Saved Queries