6.0.0-alpha14
7/2/25

[#15115] lib/Factory/Driver.php:line 55 error for pre-existing virtual address book
Summary lib/Factory/Driver.php:line 55 error for pre-existing virtual address book
Queue Turba
Queue Version 4.2.27
Type Bug
State Resolved
Priority 1. Low
Owners
Requester toli (at) lerios (dot) org
Created 07/01/2022 (1097 days ago)
Due
Updated 07/02/2022 (1096 days ago)
Assigned
Resolved 07/01/2022 (1097 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
07/02/2022 04:48:52 AM toli (at) lerios (dot) org Comment #3 Reply to this comment
This was already fixed. Please check that you are using the most up 
to date packages.
Thank you for your response, Michael (and for the patch you have 
already committed). I cannot update the Horde/Turba installation 
myself, but whenever the IT company that manages the installation 
updates Horde/Turba to a more recent version, I'll confirm that the 
bug is fixed; in the unlikely event the bug persists, I'll reopen this 
bug. Thanks again!
07/01/2022 07:33:14 PM Michael Rubinsky Comment #2
State ⇒ Resolved
Priority ⇒ 1. Low
Reply to this comment
This was already fixed. Please check that you are using the most up to 
date packages.
07/01/2022 03:27:40 PM toli (at) lerios (dot) org Comment #1
Priority ⇒ 3. High
Patch ⇒ No
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ lib/Factory/Driver.php:line 55 error for pre-existing virtual address book
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
Since the Jun 6, 2022 commit to lib/Factory/Driver.php (and later, 
related commits), virtual address books (VABs) have been broken for a 
user who had the following pre-existing VABs (see the SQL dump below; 
these are very basic VABs, nothing fancy, and therefore probably in 
wide use); all the errors generate the log entry below (see horde.log) 
and display a plain HTML page with the same error. Some workflows that 
cause this error: (1) attempting to create a new VAB for search 
produces the error (though the VAB does, in fact, get created); (2) 
the existing VABs cannot be browsed or deleted (the final step, when 
'Delete' gets pressed, delivers the error); (3) many email messages 
(but not all) cannot be displayed when double-clicking on them (prob. 
because of a VAB lookup that fails).

Again, this doesn't happen for all users, only for a user who has 
pre-existing VABs, like the ones below. It appears the issue is 
simple: the 'source' below is a string, but the Jun 6, 2022 commit 
throws an error if 'source' is not an array. So maybe the fix may be 
that, when the turba_shares rows are loaded from SQL,' source's which 
are strings must be turned into arrays before getting passed on to 
Driver.php.

horde.log error:

2022-07-01T05:46:17-05:00 EMERG: HORDE [turba] $config must be an 
array [pid 976297 on line 55 of 
"/usr/local/cpanel/base/horde/turba/lib/Factory/Driver.php"]

SQL dump of relevant table rows (email replaced with 
'nobody@nobody.com' for privacy):

INSERT INTO "turba_shares" 
VALUES(922,'t27FW8VJbiEKw01sVBO6NF4','nobody@nobody.com',0,0,0,0,'vamvakas',NULL,'a:3:{s:4:"type";s:5:"vbook";s:6:"source";s:32:"564f76d6a9885108f812ed52325f595c";s:8:"criteria";a:0:{}}',NULL);
INSERT INTO "turba_shares" 
VALUES(923,'Qfa8ky2wYRfNUTqmM8T8R7o','nobody@nobody.com',0,0,0,0,'vamecos',NULL,'a:3:{s:4:"type";s:5:"vbook";s:6:"source";s:10:"favourites";s:8:"criteria";a:0:{}}',NULL);

Saved Queries