[cvs] [Wiki] changed: FAQ/Admin/Troubleshoot/Turba

[Jan Schneider]

jan  Fri, 29 Jul 2005 08:35:11 -0700

Modified page: http://wiki.horde.org/FAQ/Admin/Troubleshoot/Turba
New Revision:  1.3
Change log:  Remove entry that has been fixed with a newer release

@@ -8,32 +8,21 @@
 [[toc]]
 
 ++++ After upgrading from Turba 1.x to Turba 2.x, all the contacts disappeared
 Your user names probably have changed. You now use realms (user at domain.tld) but you didn't use them (user) in your old Horde version, or vice versa. If you are using IMP for authentication, check the {{'realms'}} parameter in {{imp/config/servers.php}}.
-
-++++ When adding a new address from IMP I get an error that it is already in the address book.
-This is a bug in the code that has since been fixed. The error is in turba/lib/api.php at about line 93. The incorrect and correct lines are:
-
-<code>
-INCORRECT:
-    if (PEAR::isError($res) || count($res) > 0) {
-
-CORRECT:
-    if (PEAR::isError($res) || $res->count() > 0) {
-</code>
 
 ++++ Why does Turba give the error "Undefined index: socket ..."
 This means you have a missing or misconfigured //socket// and/or //protocol// parameter value in the //params// block(s) in {{/horde/turba/config/sources.php}}.
 
 Unless you are trying to use unix sockets rather than tcp/ip connections, set the //socket// value to '' (meaning no value), and/or set the //protocol// value to 'tcp'.
 
-++++ Added attribute names not working with ldap
-When adding new attribute names in the {{sources.php}} map section for ldap servers, make sure all the attribute names are completely lowercase. Also make sure that all attributes you add to {{sources.php}} are also added to {{attributes.php}}. Finally, make sure your ldap ACL's are set correctly to allow them to be viewed.
+++++ Added attribute names not working with LDAP
+When adding new attribute names in the {{sources.php}} map section for LDAP servers, make sure all the attribute names are completely lowercase. Also make sure that all attributes you add to {{sources.php}} are also added to {{attributes.php}}. Finally, make sure your LDAP ACL's are set correctly to allow them to be viewed.
 
 ++++ LDAP queries empty after upgrading to Turba 1.2
 The 'objectclass' entry for LDAP address book definitions in {{turba/config/sources.php}} is respected in Turba 1.2 but wasn't in earlier versions. Set it to use a correct value for your LDAP structure.
 
-++++ Notice: Undefined index: businesscategory
+++++ "Notice: Undefined index: businesscategory" or similar error message
 Turba has a system of defining what is in a directory or address book which is necessarily complicated by reason that it is flexible enough to map to pretty much anything with no code changes, only configuration file tweaks.
 
 In {{turba/config/sources.php}}, for every backend that you use in Turba, you configure a //map//. The map defines a mapping between whatever fields exist in the backend directory and what Turba calls those fields and also what kind of data Turba treats them as containing. So if the //contact_email// field in a database table is an email address, you could tell Turba to map 'email' => 'contact_email'.