[turba] turba Digest, Vol 1553, Issue 1

Thu Dec 8 14:25:06 UTC 2011

Quoting zBit <zbit at centrum.cz>:

>> Od: turba-request at lists.horde.org
>> Komu: <turba at lists.horde.org>
>> Datum: 30.11.2011 13:00
>> Předmět: turba Digest, Vol 1553, Issue 1
>>
>> Send turba mailing list submissions to
>> 	turba at lists.horde.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> 	http://lists.horde.org/mailman/listinfo/turba
>> or, via email, send a message with subject or body 'help' to
>> 	turba-request at lists.horde.org
>>
>> You can reach the person managing the list at
>> 	turba-owner at lists.horde.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of turba digest..."
>>
>>
>> ----------
>>
>> Today's Topics:
>>
>>   1. Upgrading Turba 2.3.2 -> 3.0.10 (Stable) (zBit)
>>   2. Failed to parse time-string -- (Simon Brereton)
>>   3. localldap and fullname for contacts: cn badly cut into	pieces
>>      (LALOT Dominique)
>>   4. Re: Upgrading Turba 2.3.2 -> 3.0.10 (Stable) (Michael J Rubinsky)
>>
>>
>> ----------
>>
>>
>> Hello,
>>
>> We need to upgrade our Horde webmail (H3.3.5 + I4.3.5 + T2.3.2)  
>> because of several problems (e.g. regarding attachments).
>> So far I have deployed new stable installation (H4.0.11 + I5.0.14 +  
>> T3.0.10) using the preferred way - pear - on our development
>> machine, changed a little overall settings using the Horde GUI  
>> administration site. As far as Turba is concerned, I merely renamed
>> sources.php to backends.php. The conf.php file as well as other  
>> Turba configuration files seem to be almost the same in both old
>> and new installations. I have imported old data into new database  
>> and run all available migrations from within the GUI administration.
>> The migrations finished without any problem as I can tell. Having  
>> both Horde and IMP ready I logged into an random e-mail account
>> but the address book looked pretty empty. Whatever account I choose  
>> its contact list is empty. I read all available (faq/install/upgrade)
>> guides but did not stumble accross something interesting in my  
>> problem. Therefore I have enabled debug while clicking on the
>> addressbook and it generated quite different SQL queries for both  
>> old and new installation. I do not know what should be wrong with
>> my configuration or where else to look at. Do you have any idea?
>>
>> OLD HORDE
>>
>> HORDE [debug] [turba] SQL Query by DataTree_sql::getAttributes():  
>> SELECT datatree_id, attribute_name AS name, attribute_key AS
>> "key", attribute_value AS value FROM horde_datatree_attributes  
>> WHERE datatree_id IN (*, *, *) [pid * on line 1085 of  
>> "horde/lib/Horde/DataTree/sql.php"]
>>
>> HORDE [debug] [turba] SQL query by Turba_Driver_sql::_search():  
>> SELECT object_id, owner_id, object_type, object_members, object
>> _uid, object_firstname, object_lastname, object_middlenames,  
>> object_nameprefix, object_namesuffix, object_alias, object_bday,  
>> object_homestreet
>> , object_homepob, object_homecity, object_homeprovince,  
>> object_homepostalcode, object_homecountry, object_workstreet,  
>> object_workpob, object_wo
>> rkcity, object_workprovince, object_workpostalcode,  
>> object_workcountry, object_tz, object_email, object_homephone,  
>> object_workphone, object_cel
>> lphone, object_fax, object_pager, object_title, object_role,  
>> object_company, object_category, object_notes, object_url,  
>> object_freebusyurl, obj
>> ect_pgppublickey, object_smimepublickey FROM turba_objects WHERE  
>> (owner_id = ? AND (LOWER(object_email) LIKE LOWER(?))) [pid * on  
>> line 168
>> of "horde/turba/lib/Driver/sql.php"]
>>
>> NEW HORDE
>>
>> DEBUG: HORDE [turba] SQL SELECT object_id, object_type, owner_id,  
>> object_nameprefix,
>>          object_firstname, object_middlenames, object_lastname,
>>          object_namesuffix FROM turba_objects WHERE (owner_id =
>>          'login at domain.xy') [pid * on line 803 of  
>> "/usr/share/php/Horde/Db/Adapter/Base.php"]
>> DEBUG: HORDE [turba] SQL SHOW FIELDS FROM `turba_objects` [pid * on  
>> line 803 of "/usr/share/php/Horde/Db/Adapter/Base.php"]
>> DEBUG: HORDE [turba] SQL SELECT object_id, object_type, owner_id,  
>> object_nameprefix,
>>          object_firstname, object_middlenames, object_lastname,
>>          object_namesuffix FROM turba_objects WHERE (object_type =  
>> 'Group' AND
>>          owner_id = 'some at email.org') [pid * on line 803 of  
>> "/usr/share/php/Horde/Db/Adapter/Base.php"]
>>
>> Kind regards,
>> David
>>
>>
>>
>> ----------
>>
>> Hi
>>
>> Today one of my users started getting an error when editing a contact...
>>
>> Anniversary A fatal error has occurred
>> Failed to parse time string (--)
>> Details have been logged for the administrator.
>>
>> However, in the logs I only see..
>>
>>
>> 2011-11-29T16:34:32+00:00 INFO: HORDE4 [horde] Finished sync of
>> database task. Failures: 0; changes from client (Add, Replace, Delete,
>> AddReplaces): 0, 0, 0, 0; changes from server (Add, Replace, Delete):
>> 0, 0, 0 [pid 2746 on line 512 of
>> "/usr/share/php/Horde/SyncMl/ContentHandler.php"]
>> 2011-11-29T16:39:05+00:00 EMERG: HORDE4 [turba] Failed to parse time
>> string (--) [pid 2525 on line 252 of "/usr/share/php/Horde/Date.php"]
>> 2011-11-29T16:39:55+00:00 EMERG: HORDE4 [turba] Failed to parse time
>> string (--) [pid 2746 on line 252 of "/usr/share/php/Horde/Date.php"]
>> 2011-11-29T16:40:31+00:00 NOTICE: HORDE4 [horde] PHP ERROR: Undefined
>> index: params [pid 2180 on line 36 of
>> "/usr/share/horde4/lib/Block/Account.php"]
>> 2011-11-29T16:40:31+00:00 WARN: HORDE4 [horde] PHP ERROR: Missing
>> argument 2 for  
>> Horde_Service_Weather_WeatherUnderground::_getCommonElements(),
>> called in /usr/share/php/Horde/Service/Weather/WeatherUnderground.php
>> on line 102 and defined [pid 2180 on line 207 of
>> "/usr/share/php/Horde/Service/Weather/WeatherUnderground.php"]
>> 2011-11-29T16:40:31+00:00 NOTICE: HORDE4 [horde] PHP ERROR: Undefined
>> variable: dewpoint [pid 2180 on line 182 of
>> "/usr/share/horde4/lib/Block/Weather.php"]
>> 2011-11-29T16:40:49+00:00 EMERG: HORDE4 [turba] Failed to parse time
>> string (--) [pid 2524 on line 252 of "/usr/share/php/Horde/Date.php"]
>> 2011-11-29T16:41:21+00:00 EMERG: HORDE4 [turba] Failed to parse time
>> string (--) [pid 2971 on line 252 of "/usr/share/php/Horde/Date.php"]
>> 2011-11-29T16:43:56+00:00 EMERG: HORDE4 [turba] Failed to parse time
>> string (--) [pid 2525 on line 252 of "/usr/share/php/Horde/Date.php"]
>>
>>
>> This happens for any and all contacts and when I look at the record in
>> the turba_objects, the item doesn't even have an anniversary entry
>> (it's blank).
>>
>> Any ideas?
>>
>> Thanks.
>>
>> Simon
>>
>>
>>
>> ----------
>>
>> Problem with ldap backend and some names.
>> last version of turba:
>>
>> If the cn is ldap is:
>> LE BORGNE Kevin
>>
>> in imp, we can see:
>> BORGNE, Kevin LE
>>
>> There is a bad cut of cn and I don't understand where exactly I can say:
>> just preserve displayname or cn
>>
>> Thanks in advance
>>
>> Dom
>>
>>
>> --
>> Dominique LALOT
>> Ingénieur Systèmes et Réseaux
>> http://annuaire.univmed.fr/showuser.php?uid=lalot
>>
>>
>>
>> ----------
>>
>>
>> Quoting zBit <zbit at centrum.cz>:
>>
>>> Hello,
>>>
>>> We need to upgrade our Horde webmail (H3.3.5 + I4.3.5 + T2.3.2)
>>> because of several problems (e.g. regarding attachments).
>>> So far I have deployed new stable installation (H4.0.11 + I5.0.14 +
>>> T3.0.10) using the preferred way - pear - on our development
>>> machine, changed a little overall settings using the Horde GUI
>>> administration site. As far as Turba is concerned, I merely renamed
>>> sources.php to backends.php. The conf.php file as well as other
>>> Turba configuration files seem to be almost the same in both old
>>> and new installations. I have imported old data into new database
>>> and run all available migrations from within the GUI administration.
>>> The migrations finished without any problem as I can tell. Having
>>> both Horde and IMP ready I logged into an random e-mail account
>>> but the address book looked pretty empty. Whatever account I choose
>>> its contact list is empty. I read all available (faq/install/upgrade)
>>> guides but did not stumble accross something interesting in my
>>> problem. Therefore I have enabled debug while clicking on the
>>> addressbook and it generated quite different SQL queries for both
>>> old and new installation. I do not know what should be wrong with
>>> my configuration or where else to look at. Do you have any idea?
>>>
>>> OLD HORDE
>>>
>>> HORDE [debug] [turba] SQL Query by DataTree_sql::getAttributes():
>>> SELECT datatree_id, attribute_name AS name, attribute_key AS
>>> "key", attribute_value AS value FROM horde_datatree_attributes WHERE
>>> datatree_id IN (*, *, *) [pid * on line 1085 of
>>> "horde/lib/Horde/DataTree/sql.php"]
>>>
>>> HORDE [debug] [turba] SQL query by Turba_Driver_sql::_search():
>>> SELECT object_id, owner_id, object_type, object_members, object
>>> _uid, object_firstname, object_lastname, object_middlenames,
>>> object_nameprefix, object_namesuffix, object_alias, object_bday,
>>> object_homestreet
>>> , object_homepob, object_homecity, object_homeprovince,
>>> object_homepostalcode, object_homecountry, object_workstreet,
>>> object_workpob, object_wo
>>> rkcity, object_workprovince, object_workpostalcode,
>>> object_workcountry, object_tz, object_email, object_homephone,
>>> object_workphone, object_cel
>>> lphone, object_fax, object_pager, object_title, object_role,
>>> object_company, object_category, object_notes, object_url,
>>> object_freebusyurl, obj
>>> ect_pgppublickey, object_smimepublickey FROM turba_objects WHERE
>>> (owner_id = ? AND (LOWER(object_email) LIKE LOWER(?))) [pid * on
>>> line 168
>>> of "horde/turba/lib/Driver/sql.php"]
>>>
>>> NEW HORDE
>>>
>>> DEBUG: HORDE [turba] SQL SELECT object_id, object_type, owner_id,
>>> object_nameprefix,
>>>           object_firstname, object_middlenames, object_lastname,
>>>           object_namesuffix FROM turba_objects WHERE (owner_id =
>>>           'login at domain.xy') [pid * on line 803 of
>>> "/usr/share/php/Horde/Db/Adapter/Base.php"]
>>> DEBUG: HORDE [turba] SQL SHOW FIELDS FROM `turba_objects` [pid * on
>>> line 803 of "/usr/share/php/Horde/Db/Adapter/Base.php"]
>>> DEBUG: HORDE [turba] SQL SELECT object_id, object_type, owner_id,
>>> object_nameprefix,
>>>           object_firstname, object_middlenames, object_lastname,
>>>           object_namesuffix FROM turba_objects WHERE (object_type =
>>> 'Group' AND
>>>           owner_id = 'some at email.org') [pid * on line 803 of
>>> "/usr/share/php/Horde/Db/Adapter/Base.php"]
>>>
>>
>> Looks like you didn't migrate the share data from the datatree to one
>> of the sql share drivers. See the UPGRADING file for Horde and Turba.
>>
>> --
>> mike
>
> I've run the following scripts as docs/UPGRADING suggest but still  
> cannot see my contacts.
>
> /usr/bin/horde-db-migrate
> /usr/bin/turba-convert-datatree-shares-to-sql
> /usr/bin/horde-convert-datatree-groups-to-sql
> /usr/bin/horde-convert-datatree-perms-to-sql
> /usr/bin/horde-move-history-out-of-datatree
>
> Is there yet another migration script I could have missed?

What share driver are you using?

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org