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 |
Taken from Chuck Hagenbuch
State ⇒ Resolved
Thanks Gunnar!
Queue ⇒ Turba
Priority ⇒ 2. Medium
look at it and moving to the Turba queue
Taken from Gunnar Wrobel
New Attachment: HK-GW-vbooks.patch
ability to search them. So I'm guessing the Kolab code doesn't handle
complex searches properly.
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!
Assigned to Gunnar Wrobel
Taken from Chuck Hagenbuch
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")
Queue ⇒ Kolab
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
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!