[turba] Questions pertaining to turba 2.1.2 behavior

[Jan Schneider]

Zitat von "John H. Bennett III" <bennettj at thebennetthome.com>:

> First, in the docs/upgrading section about synchronization support, it
> states you need to create a history backend in horde's configuration.  I
> don't seem to have this option available to me with horde 3.1.3.  When I go
> to admin/setup/horde, should I have a new tab for this, or I'm I just blind
> and can't see it?

The description is not quite correct, you only need to create the  
horde_histories table.

> Second, I have two sources defined in sources.php, localldap and localsql.
> When I choose turba from the menu, I can see in my logs that I immediately
> bind to the ldap source and I keep querying ldap even when I go into turba
> options.  Why is that, or do I have something set up incorrectly?  In the
> 2.0.5 version, I don't see this.

This is because you can now create cross-source distribution list,  
thus we need to search for potential target lists in all sources on  
every request to build the html widgets.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/