Solved!  There was a configuration problem in the sources.php that 
made every request timeout on a non-active data source.



Thanks for you help,

Chris.

Hi Michael,
You were very right, the database encoding was indeed incorrect.   
Thanks for fixing this and sorry for the bogus bug report.



However, Turba still doesn't work properly.  The combination 
Horde/IMP/Kronolith work just fine, enabling Turba makes the system 
performance go down to an unusable level (minutes per page request!).   
There are no error message in the Horde log, psql log or Apache log... 
so, I'm in the dark about what could cause this behavior.



The login is still enabled if you'd care to take a look.



Thanks,

Chris,

This is a configuration error: Based on your personal email to me 
(relevent snippits below for reference) your datatree, indeed 
everything that uses a database is broken due to an incorrect charset 
setting for your database.  I corrected in your config using the test 
login you provided.



Please re-enable Turba to verify this is working for you now.



---Snippits of email---



I looked at the datatree table in the db and this table was already 
completely empty!

So, I guess the problem is probably not Turba specific (although I 
only get Turba errors,

nothing from IMP or Horde).  Executing the delete query you proposed 
through the sql

shell (although it was empty already) gave the extensive error log 
attached to this

message (contains the db password of the test setup hence the private email).



---Relevent portion of error message, sensitive data removed---

delete from horde_datatree where group_uid='horde.shares.turba';

Results



object(DB_Error)#14 (8) {

   ["error_message_prefix"]=>

   string(0) ""

   ["mode"]=>

   int(1)

   ["level"]=>

   int(1024)

   ["code"]=>

   int(-2)

   ["message"]=>

   string(22) "DB Error: syntax error"

   ["userinfo"]=>

   string(196) "d e l e t e   f r o m   h o r d e _ d a t a t r e e   
w h e r e   g r o u p _ u i d = ' h o r d e . s h a r e s . t u r b a 
' ;  [nativecode=ERROR:  syntax error at or near "d" at character 1]"

If this is the first time you clicked on the address book icon, then 
turba was trying to create your default share.  The value in the SQL 
statement that is causing problems should be the name of the source 
that the share is for....if you didn't change anything in sources.php, 
this should be 'localsql'.  Why the SQL statement is broken, I have no 
idea yet...



Can you: (assuming this is not a production box)

Clear the turba share datatree by going to the SQL shell and typing:

delete from horde_datatree where group_uid='horde.shares.turba';



In lib/Driver.php, after line 1030 add:

line 1030: $params = array('sourceType' => $shareName);



newlines:

    echo '<pre>';

    var_dump($params);

    echo '</pre>';



Now try to return to Turba and please provide the output  of the 
var_dump as an attachment to this ticket...



Thanks.

I just installed turba and kronolith for testing purposes and just 
clicked on the address book icon.  SInce installing turba everything 
goes very very slow (where before it actually worked quite efficiently).



I can provide you with a test login if that would help.



Cheers,

Chris.



---

Can you please post more information:  What you were doing when this 
error occurs (creating a new address book?), the values you were using 
etc...



Thanks.

turba-h3-2.1-rc2 on PSQL 7.4 gives the following error:



2006-02-14 01:04:43 [16705] LOG:  statement: INSERT INTO 
horde_datatree (datatree_id, group_uid, datatree_name, datatree_order, 
datatree_data, user_uid, datatree_serialized, datatree_parents) VALUES 
(25, 'horde.shares.turba', 'l

2006-02-14 01:04:43 [16705] ERROR:  unterminated quoted string at or 
near "'l" at character 182



I can provide more information and testing if requested.



Best regards,

Chris.