6.0.0-beta1
7/22/25

[#7239] imp does not search in all available turba addressbooks
Summary imp does not search in all available turba addressbooks
Queue IMP
Queue Version 4.2
Type Bug
State Not A Bug
Priority 2. Medium
Owners
Requester mbiebl (at) gmail (dot) com
Created 08/26/2008 (6174 days ago)
Due
Updated 09/22/2008 (6147 days ago)
Assigned
Resolved 09/02/2008 (6167 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
09/22/2008 04:36:11 AM Michael Slusarz Comment #8 Reply to this comment
I can supply further information if required.
Further information is not helpful.  You will have to point to the 
exact location in the code where this is not working for you (since it 
works for everyone else with the various fixes discussed herein).
09/19/2008 01:47:44 AM mbiebl (at) gmail (dot) com Comment #7 Reply to this comment
This is the same as bug #7357.  The fix applied there also fixes the
autocompletion in IMP.  However, what Michael stated is true.  If you
set the addressbooks preference (and make sure a previously stored
user preference isn't overriding it), it will also fix this problem.
Please reopen this bug report!



It's definitely not a configuration issue.



Even after applying the fix mentioned in #7357, the search function 
does not look in all address book.

In my case, the autocompletion only finds entries from localldap, but 
not localsql and favourites.



I can supply further information if required.


09/18/2008 05:43:33 PM morgan (at) orst (dot) edu Comment #6 Reply to this comment
This is the same as bug #7357.  The fix applied there also fixes the 
autocompletion in IMP.  However, what Michael stated is true.  If you 
set the addressbooks preference (and make sure a previously stored 
user preference isn't overriding it), it will also fix this problem.
09/02/2008 08:39:45 PM mbiebl (at) gmail (dot) com Comment #5 Reply to this comment
Have you read my bug report?
I've defined the address books which to search for in imp
No you didn't.  Defining a default value in imp's prefs.php is
irrelevant - what is relevant is what the value is for the user you
are testing with.  Default values are overwritten by a user's value.
And what you are describing is precisely what happens in this case.
The user value is not set, i.e. it is empty.

I tested with a pristine account without any custom configurations and 
it didn't work either.



It worked with horde 3.1 and imp 4.1.

So there is a regression.
09/02/2008 08:25:37 PM Michael Slusarz Comment #4 Reply to this comment
Have you read my bug report?
I've defined the address books which to search for in imp
No you didn't.  Defining a default value in imp's prefs.php is 
irrelevant - what is relevant is what the value is for the user you 
are testing with.  Default values are overwritten by a user's value.   
And what you are describing is precisely what happens in this case.
09/02/2008 08:01:13 PM mbiebl (at) gmail (dot) com Comment #3 Reply to this comment
You need to define which addressbook(s) to search in IMP's preferences.
Have you read my bug report?

I've defined the address books which to search for in imp
09/02/2008 05:20:30 PM Michael Slusarz Comment #2
State ⇒ Not A Bug
Reply to this comment
You need to define which addressbook(s) to search in IMP's preferences.
08/26/2008 07:48:15 AM mbiebl (at) gmail (dot) com Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ imp does not search in all available turba addressbooks
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
I've defined three addressbooks in turba/conf/sources.php (in that order)

localsql (sql based private addressbook)

localldap (ldap based, readonly addressbook)

favourites (sql based)



If I compose a new message in IMP, the autocompletion only looks in my 
localsql addressbook



In imp/config/prefs.php I've set

$_prefs['search_sources'] = array(

     'value' => "localldap\tlocalsql\tfavourites",

     'locked' => false,

     'shared' => false,

     'type' => 'implicit');



And in turba/config/prefs.php

  $_prefs['addressbooks'] = array(

     'value' => '', <- all addressbook should be used/displayed

     'locked' => false,

     'shared' => false,

     'type' => 'implicit',

);





If I change the order in turba/conf/sources.php (e.g. make localldap 
the first one), then new first addressbook is searched.



So it seems that instead of querieng all available addressbooks only 
the first one in turba/conf/sources.php is used

Saved Queries