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

Fri Jul 29 06:53:07 PDT 2005

guest [193.134.2.2]  Fri, 29 Jul 2005 06:53:07 -0700

Modified page: http://wiki.horde.org/FAQ/Admin/Troubleshoot
New Revision:  2.0
Change log:  Revert

@@ -4,18 +4,8 @@
 
 [[toc]]
 
 +++ Common error messages
-
-++++ "Only variable references should be returned by reference"
-++++ "Only variables can be passed by reference"
-These messages appear after upgrading to PHP 4.4 or PHP 5.1. These PHP versions raise notices about reference usage that older version accepted happily. Only Horde 3.x and the H3 application versions will be fixed to not cause this messages, so either upgrade to the latest versions, or set your error reporting level in PHP to exclude E_NOTICE level messages.
-
-E.g. in {{php.ini}}:
-
-<code>
-error_reporting = E_ALL & ~E_NOTICE
-</code>
 
 ++++ "Document contains no data"
 The Netscape error message, "Document contains no data", only tells you that nothing was sent from the web server to the browser. In other words, something went quite wrong, yet you've no idea what.
 
@@ -498,61 +488,4 @@
 From http://lists.horde.org/archives/imp/Week-of-Mon-20030203/029747.html.
 
 ++++ IMP displays "There are no parts that can be displayed inline" for all my messages.
 This is a known problem with PHP 4.2.2/4.2.3 and certain versions of the UW IMAP c-client. If using these PHP versions, either downgrade to UW IMAP c-client 2001a or upgrade to PHP 4.3.0.
-
-+++ Troubleshooting Turba
-
-++++ 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.
-
-++++ 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
-
-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'.
-
-However, Turba needs to then know what 'email' or 'name' are. They're defined in {{turba/config/attributes.php}}, which is the set of attributes that any given Turba installation understands. The {{attributes.php}} file defines the label for a field and also what kind of data it is - a string, an email address, an enumeration of several options, etc.
-
-So, back to the problem: you have some attributes in your map that Turba doesn't know about. In {{sources.php}}, there's probably a line something like:
-
-<code type="php">
-'businesscategory' => 'backend_field_bus_cat',
-</code>
-
-But there is no 'businesscategory' attribute in your attributes.php. You need to either add an attribute entry, or remove that field, or map it to something else that Turba already knows about.
-
-In some versions of Turba, the default sources.php file included an example that used attributes that weren't in the default attributes.php file and hence could cause this error. This has since been fixed for newer releases. 
-
-+++ Troubleshooting Trean
-
-++++ Can't save bookmarks or categories.
-This usually means one of the following:
-
-* You didn't properly setup your Horde categories driver in {{horde/config/conf.php}}.
-* You set your categories driver to something which can't save data between sessions (like the "session" or "none" drivers.
-* You failed to create the needed category storage for your category setup (e.g. didn't create the database tables when using the sql driver).
-
-+++ Troubleshooting Chora
-
-++++ Why do I get a //404, Object not found// error when clicking on any cvsroot subdirectories?
-Some web servers do not support PATH_INFO, or have it disabled by default, in which case this problem will arise. Try to disable PATH_INFO usage by setting {{$conf['options']['use_path_info']}} to false in {{horde/chora/config/conf.php}}.
