| Summary | Different default directories for search and browse |
| Queue | Turba |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Accepted |
| Priority | 1. Low |
| Owners | |
| Requester | kkonstan (at) duth (dot) gr |
| Created | 03/28/2008 (44 days ago) |
| Due | |
| Updated | 04/04/2008 (37 days ago) |
| Assigned | |
| Resolved | |
| Attachments | |
| Milestone | |
| Patch |
Priority ⇒ 1. Low
State ⇒ Accepted
Separate preference for browsing and searching address books sounds like too much overhead to me. But automatically picking the first browseable address book from the addresbooks preference if the default address book is not browseable seems to be a good idea.Patch ⇒
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ Different default directories for search and browse
Type ⇒ Enhancement
Priority ⇒ 2. Medium
State ⇒ New
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).