6.0.0-alpha14
7/1/25

[#5476] Possibly invalid VBook search criteria
Summary Possibly invalid VBook search criteria
Queue Turba
Queue Version HEAD
Type Bug
State Resolved
Priority 2. Medium
Owners mrubinsk (at) horde (dot) org
Requester wrobel (at) horde (dot) org
Created 06/19/2007 (6587 days ago)
Due
Updated 03/20/2008 (6312 days ago)
Assigned 06/19/2007 (6587 days ago)
Resolved 03/20/2008 (6312 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/20/2008 01:50:50 PM Michael Rubinsky Comment #5
Taken from Chuck Hagenbuch
State ⇒ Resolved
Reply to this comment
Well, that was easy...



Thanks Gunnar!
03/20/2008 01:36:57 PM Michael Rubinsky Assigned to Michael Rubinsky
 
03/20/2008 01:36:38 PM Michael Rubinsky Version ⇒ HEAD
Queue ⇒ Turba
Priority ⇒ 2. Medium
 
03/20/2008 01:36:04 PM Michael Rubinsky Comment #4 Reply to this comment
I can confirm that v address books are currently broken....taking a 
look at it and moving to the Turba queue
03/20/2008 12:40:24 PM Gunnar Wrobel Assigned to Chuck Hagenbuch
Taken from Gunnar Wrobel
 
03/20/2008 12:40:11 PM Gunnar Wrobel Comment #3
New Attachment: HK-GW-vbooks.patch Download
Reply to this comment
VBooks work fine for me, and what your patch does is remove the
ability to search them. So I'm guessing the Kolab code doesn't handle
complex searches properly.
Indeed :)



Took me a while to get back to this one. I did fix the search in the 
Kolab driver now and now the problems vanished. I just misunderstood 
how searching worked in Turba.



There was still one thing I needed to tweak though:



When defining a virtual address book based on a Share Turba did not 
recognize the original source. A suggested patch is attached but I 
admit that I'm not 100% certain if this is acceptable because if that 
patch is okay I would assume that vbooks based on SQL Shares would be 
broken too. Maybe you can check this one.



Thanks!
06/19/2007 07:13:33 PM Chuck Hagenbuch Comment #2
Assigned to Gunnar Wrobel
Taken from Chuck Hagenbuch
Reply to this comment
VBooks work fine for me, and what your patch does is remove the 
ability to search them. So I'm guessing the Kolab code doesn't handle 
complex searches properly.



(VBooks are searchable, which is an additive filter - so if the vbook 
returns everyone with an email address @horde.org, you can still 
search that VBook for just "chuck")
06/19/2007 07:12:27 PM Chuck Hagenbuch Version ⇒
Queue ⇒ Kolab
 
06/19/2007 07:11:49 PM Chuck Hagenbuch Deleted Original Message
 
06/19/2007 10:49:15 AM Jan Schneider State ⇒ Assigned
 
06/19/2007 10:30:08 AM Gunnar Wrobel Assigned to Chuck Hagenbuch
 
06/19/2007 10:29:35 AM Gunnar Wrobel Comment #1
Priority ⇒ 1. Low
State ⇒ Unconfirmed
New Attachment: turba-lib-Driver-vbook.php_search-criteria_20070619.patch
Queue ⇒ Turba
Summary ⇒ Possibly invalid VBook search criteria
Type ⇒ Bug
Reply to this comment
The VBook driver in Turba currently does not work for me when using 
the Kolab Driver. The problem are the search criteria generated by the 
vbook.php driver.



To me it looks like there is one level of arrays too much and I 
attached a suggested patch.



But I'm not absolutely certain that this is indeed the case since 
Chucks commit messages looked like vbooks worked for him. So maybe 
there is also a problem with the search function within the kolab 
driver.



Thanks!

Saved Queries