[Tickets #2269] NEW: Turba tries to browse unbrowseable address books

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=2269
-----------------------------------------------------------------------
 Ticket             | 2269
 Created By         | kevin_myer at iu13.org
 Summary            | Turba tries to browse unbrowseable address books
 Queue              | Turba
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-07-14 10:41) wrote:

I have multiple address books configured to use and have selected which ones
to use and the order they will be displayed and searched.

For simplicity's sake, I'll use two for an example.

1) LDAP directory - physically read-only, browse -> false
2) localsql - My Addressbook, read/write

When I click on the browse button, there is a very perceptible five second
or so pause and then the following notification: "Your default addressbook
is not browseable."  A list of browseable addressbooks (in this case, and
actually all current cases for our installation) is shown in the upper
right, with My Addressbook.

It seems that if Browse is chosen from the menu, the first available
browseable address book should be browsed, instead of trying the default,
finding all the results, then checking to see if its browsable.  I'm just
speculating that's what's happening, based on the timing of how long a
search for all users normally takes.