[Tickets #10127] Setting Horde to use SQL Session Handling breaks Kronolith

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10127
------------------------------------------------------------------------------
  Ticket             | 10127
  Created By         | simon at simonandkate.net
  Summary            | Setting Horde to use SQL Session Handling breaks
                     | Kronolith
  Queue              | Kronolith
  Version            | 3.0.3
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


simon at simonandkate.net (2011-05-26 08:27) wrote:

Wasn't sure whether to put this in the Horde or Kronolith queue, but  
figured in the end that it is K that shows the issues.

First noticed it with 3.0.2, but still does it in 3.0.3.

Horde 4.0.2
Kronolith 3.0.2

Leaving Horde Custom Session Handler as php session handler, Kronolith  
works fine. Connects to its SQL backend and works.

If I tell Horde to use SQL as its session handler, Kronolith displays  
"Error when communicating with the server" messages (two) appearing in  
the client screen. Existing appointments still show, and further  
(same) errors appear over time. Making a new appointment appears to  
work, but exiting Kronolith and coming back in it has not been saved.

Set Horde back to use PHP session handler, and Kronolith works again.

Apache log has lots of these:

[Wed May 18 21:57:12 2011] [error] [client 192.168.1.155] PHP Fatal  
error:  Exception thrown without a stack frame in Unknown on line 0

Horde error log throws this:

2011-05-18T22:06:02+10:00 NOTICE: HORDE [kronolith] PHP ERROR:  
Undefined index:  api [pid 300 on line 1218 of  
"/var/www/horde4/kronolith/lib/Kronolith.php"]