[Tickets #14099] Current Horde_Core requires interface not provided by current Kolab_Storage (breaks Horde under some configurations)

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14099
------------------------------------------------------------------------------
  Ticket             | 14099
  Created By         | pez at apocalyptech.com
  Summary            | Current Horde_Core requires interface not provided by
                     | current Kolab_Storage (breaks Horde under some
                     | configurations)
  Queue              | Horde Framework Packages
  Type               | Bug
  State              | Unconfirmed
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


pez at apocalyptech.com (2015-09-06 06:06) wrote:

The commit in question is this one:  
https://github.com/horde/horde/commit/1496bd21af11361e52ea0e5a161aa7717a5f84ab

In that commit, a new interface is defined in  
framework/Kolab_Storage/lib/Horde/Kolab/Storage/HistoryPrefix.php, and  
a class is set to use that interface, at  
framework/Core/lib/Horde/Core/Kolab/Storage/HistoryPrefix.php.

The current stable Horde_Kolab_Storage (2.1.4) does not provide the  
interface (since 2.1.4 was cut sometime 'round April 28, and that  
commit was from May 18).  The current stable Horde_Core (2.20.9) DOES  
contain the class which attempts to use that interface, since that  
project's been cut a few times since the commit in question.

Under some configurations, this can lead to a fatal error like the following:

2015-09-05T23:01:17-05:00 EMERG: HORDE [turba] Interface  
'Horde_Kolab_Storage_HistoryPrefix' not found [pid 8128 on line 21 of  
"/usr/share/pear/Horde/Core/Kolab/Storage/HistoryPrefix.php"]

Specifically in my case, I'd had my Horde Shares Driver set to  
"IMAP/Kolab," which caused that error to pop up whenever Turba was  
active.  When I changed that setting to SQL, I was able to use Horde  
properly.  The error wasn't restricted to just Turba - it would  
prevent all access to Horde.