[imp] Compose and the default Address Book

[Torbjorn Grindhaug]

I've tried with these settings now, but it's the same result.
Setting the display order to show localsql first makes the localsql
the default when pressing browsebutton in the turba-application, but
setting the shared ldap addressbook first makes the localsql the
default when pressing the addressbook-button in the composewindow.

The localsql-addressbook was the default in both scenarios when under
Horde 3.1.1/IMP 4.1.1/Turba 2.1.1.
It was after the last upgrade this behavior changed for us.
I've tried with both Horde 3.1.4/3.1.5, IMP 4.1.4/4.1.5 and Turba 2.1.4/2.1.5

On 10/25/07, Andrew Morgan <morgan at orst.edu> wrote:
> On Thu, 25 Oct 2007, Torbjorn Grindhaug wrote:
>
> > I've tried changing these settings, but with no luck.
> > There is one thing we have noticed though. When reversing the display
> > order of the addressbooks in turba (putting the shared
> > ldap-addressbook first), then the localsql-addressbook will be the one
> > used as default in the compose-window in imp. But now, as we don't
> > have the shared-addressbook set as browseable in sources.php, it will
> > show an error-message pressing "browse" in turba.
> > For me it seems like the turba browsefunction chooses the "right"
> > addressbook, but the imp-compose-addressbook-function chooses the
> > other.
> >
> > Any ideas?
>
> My localsql source has these settings:
>
>      'export' => true,
>      'browse' => true,
>      'use_shares' => false,
>
>
> and my localldap source has these settings:
>
>      'export' => false,
>      'browse' => false,
>      'use_shares' => false
>
>
>         Andy
>