[Tickets #6536] Different default directories for search and browse

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6536
-----------------------------------------------------------------------
 Ticket             | 6536
 Created By         | kkonstan at duth.gr
 Summary            | Different default directories for search and browse
 Queue              | Turba
 Version            | FRAMEWORK_3
 Type               | Enhancement
 State              | New
 Priority           | 2. Medium
 Milestone          | 
 Patch              | 
 Owners             | 
-----------------------------------------------------------------------


kkonstan at duth.gr (2008-03-28 17:48) wrote:

Our installation has a read only non-browsable LDAP directory and a
per-user SQL addressbook. I used the permissions system to make LDAP read
only, so adding/modifying etc only works for SQL.

If the order of the addressbooks is set like that:

$_prefs['addressbooks'] = array(
    'value' => "localldap\nlocalsql",

Then browse.php gives a warning that the default addressbook is not
browsable every time I pick "Turba" from the menu or from the sidebar,
which is confusing our users. There is of course no addressbook selection
wizard, since there is only one choice; localsql. Perhaps it should try the
next on the list if the first one is not browsable instead of returning an
error?

I can change the order so that localsql is first, but then search.php's
addressbook selection wizard defaults to the first one, which is localsql,
and not localldap, the addressbook the vast majority of the users would
like to search.

Ideally, it should be tunable by prefs.php or conf.php so that both
browse.php and search.php could have a seperate default addressbook setting
(ie SQL for browse, LDAP for search).