Copy::from::ldap::to::My_Address_Book::problem

Hello list,

we upgraded from turba 2.1 to turba 2.3.

if we copy a contact from the ldap addressbook to the 'My Address Book'(sql)
it actually adds the contact to the 'My Address Book' BUT with 'Blank name' in the name column.
we did the upgrade like descibed in turba/docs/UPGRADING.

any hint how to fix that?

thank's Rafael

_________________________________________________________________
More than messages–check out the rest of the Windows Live™.
http://www.microsoft.com/windows/windowslive/
--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org

Re: Copy::from::ldap::to::My_Address_Book::problem

Zitat von Rafael Berez <idcommunication <at> hotmail.com>:

>
> Hello list,
>
> we upgraded from turba 2.1 to turba 2.3.
>
> if we copy a contact from the ldap addressbook to the 'My Address Book'(sql)
> it actually adds the contact to the 'My Address Book' BUT with  
> 'Blank name' in the name column.
> we did the upgrade like descibed in turba/docs/UPGRADING.
>
> any hint how to fix that?

How are the several name (parts) mapped for those sources in  
config/sources.php?

Jan.

--

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

--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org

Fwd: RE: Copy::from::ldap::to::My_Address_Book::problem

----- Weitergeleitete Nachricht von idcommunication <at> hotmail.com -----
     Datum: Mon, 8 Jun 2009 14:18:16 +0200
       Von: Rafael Berez <idcommunication <at> hotmail.com>
   Betreff: RE: [turba] Copy::from::ldap::to::My_Address_Book::problem
        An: jan <at> horde.org

Hey,

thank's for reply...

the mapping for the sql addressbook is:

$cfgSources['localsql'] = array(
    'title' => _("My Address Book"),
    'type' => 'sql',
(...)
 'map' => array(
        '__key' => 'object_id',
        '__owner' => 'owner_id',
        '__type' => 'object_type',
        '__members' => 'object_members',
        '__uid' => 'object_uid',
        'firstname' => 'object_firstname',
        'lastname' => 'object_lastname',
        'middlenames' => 'object_middlenames',
        'namePrefix' => 'object_nameprefix',
        'nameSuffix' => 'object_namesuffix',
        'name' => array('fields' => array('firstname', 'lastname'),
                         'format' => '%s %s'),

keep turba in sync with employees DB

Hello,

we have a oracle DB with data about our employees that include 
phonenumber and mail. We would like to keep the turba address book ( 
postgres ) in sync with this oracle DB using a perl script that should 
be called by cron every night.

Is there documentation on how turba stores the data in in the postgres 
tables the way we can access them via DBD:pg  or is there a simple API ?

Thanks
Andreas

--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org

Re: keep turba in sync with employees DB

Quoting Andreas Moroder <andreas.moroder <at> sb-brixen.it>:

> Hello,
>
> we have a oracle DB with data about our employees that include  
> phonenumber and mail. We would like to keep the turba address book (  
> postgres ) in sync with this oracle DB using a perl script that  
> should be called by cron every night.
>
> Is there documentation on how turba stores the data in in the  
> postgres tables the way we can access them via DBD:pg  or is there a  
> simple API ?

Turba has methods such search, getContact, replace, and import that  
could be used for something like this.  However, if what your doing is  
simply updating a few fields of existing contacts, it might be easier  
for you to modify the turba_objects table directly. Most of the fields  
in the turba_objects table are self explanatory. Some that might not  
be include the object_id - a locally unique identifier, object_uid - a  
globally unique identifier used mostly for syncing, owner_id - this is  
either the username of the owner of the contact (if not using a shared  
source) or the id of the share that represents the address book this  
contact belongs to, object_type would always be "Object" for a  
contact, object_members is only used when the entry defines a contact  
group and contains a serialized hash of the contact ids that it  
contains.

HTH

Re: keep turba in sync with employees DB

> 
> Turba has methods such search, getContact, replace, and import that 
> could be used for something like this.  However, if what your doing is 
> simply updating a few fields of existing contacts, it might be easier 
> for you to modify the turba_objects table directly. Most of the fields 
> in the turba_objects table are self explanatory. Some that might not be 
> include the object_id - a locally unique identifier, object_uid - a 
> globally unique identifier used mostly for syncing, owner_id - this is 
> either the username of the owner of the contact (if not using a shared 
> source) or the id of the share that represents the address book this 
> contact belongs to, object_type would always be "Object" for a contact, 
> object_members is only used when the entry defines a contact group and 
> contains a serialized hash of the contact ids that it contains.
> 
> HTH
> 
> Thanks,
> mike
> 
Hello Mike,

when employees quit or new one begin I have to delete or add records 
from the main address book. This looks a little bit complicated. 
Probably the  best way would be to delete all the records of this 
address book and reimport all. Because this entries will never be 
synched with a phone or so it should not be a problem that they change id.
I found the import_vcards.php script, but cannot find two things:

- instructions on how to start a php script from the command line
- a script that deletes the entries of a address book

Re: keep turba in sync with employees DB

Quoting Andreas Moroder <andreas.moroder <at> sb-brixen.it>:

>>
>> Turba has methods such search, getContact, replace, and import that  
>> could be used for something like this.  However, if what your doing  
>> is simply updating a few fields of existing contacts, it might be  
>> easier for you to modify the turba_objects table directly. Most of  
>> the fields in the turba_objects table are self explanatory. Some  
>> that might not be include the object_id - a locally unique  
>> identifier, object_uid - a globally unique identifier used mostly  
>> for syncing, owner_id - this is either the username of the owner of  
>> the contact (if not using a shared source) or the id of the share  
>> that represents the address book this contact belongs to,  
>> object_type would always be "Object" for a contact, object_members  
>> is only used when the entry defines a contact group and contains a  
>> serialized hash of the contact ids that it contains.
>>
>> HTH
>>
>> Thanks,
>> mike
>>
> Hello Mike,
>
> when employees quit or new one begin I have to delete or add records  
> from the main address book. This looks a little bit complicated.  
> Probably the  best way would be to delete all the records of this  
> address book and reimport all. Because this entries will never be  
> synched with a phone or so it should not be a problem that they  

turba 2.1 to 2.2 migration problem.

Hi all:

I setup a new server to replace my old server and migrate all MySQL data
from old server to new server but new server has new version of horde
included turba 2.3.1. after all things done. I can't see my address book.
Please help.

Following is my step. hope it would help.

1.run 2.1_to_2.2_add_sql_share_tables.sql and
convert_datatree_shares_to_sql.php without errors.
2.export mysql data from old server to new server.
3.login to new server. check for address book. only showed the global shared
address book. the personal address book gone.....
4.I found some account can read its address book with
[attribute_params]='a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:5:"aaaaa";}'
5.I tried to create personal address book for the user which can't read its
personal address book. to check if the address book created all contacts
back. but failed. and I found the [attribute_params] in this account is like
this
'a:3:{s:6:"source";s:8:"localsql";s:4:"name";s:32:"7b7b3ecea5a9d1c591a40e83067d29c8";s:7:"default";b:0;}'
6.I try to update the [attribute_params] from
'a:3:{s:6:"source";s:8:"localsql";s:4:"name";s:32:"7b7b3ecea5a9d1c591a40e83067d29c8";s:7:"default";b:0;}'
to
'a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:4:"bakk";}'
and the contact for that user bakk comes back.
7.so I update all users attribute_params to
'a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:5:"aaaaa";}'.
to see if it works. but failed.
8.I have to create personal address book for the user whose address book

turba 2.1 to 2.3.1 migration problem.

Hi all:
Sorry I wrote a wrong subject. Repost.

I setup a new server to replace my old server and migrate all MySQL data
from old server to new server but new server has new version of horde
included turba 2.3.1. after all things done. I can't see my address book.
Please help.

Following is my step. hope it would help.

1.run 2.1_to_2.2_add_sql_share_tables.sql and
convert_datatree_shares_to_sql.php without errors.
2.export mysql data from old server to new server.
3.login to new server. check for address book. only showed the global shared
address book. the personal address book gone.....
4.I found some account can read its address book with
[attribute_params]='a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:5:"aaaaa";}'
5.I tried to create personal address book for the user which can't read its
personal address book. to check if the address book created all contacts
back. but failed. and I found the [attribute_params] in this account is like
this
'a:3:{s:6:"source";s:8:"localsql";s:4:"name";s:32:"7b7b3ecea5a9d1c591a40e83067d29c8";s:7:"default";b:0;}'
6.I try to update the [attribute_params] from
'a:3:{s:6:"source";s:8:"localsql";s:4:"name";s:32:"7b7b3ecea5a9d1c591a40e83067d29c8";s:7:"default";b:0;}'
to
'a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:4:"bakk";}'
and the contact for that user bakk comes back.
7.so I update all users attribute_params to
'a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:$length_of_owner_id:"$owner_id";}'.
to see if it works. but failed.

Re: turba 2.1 to 2.2 migration problem.

On 06/18/2009 04:13 PM, Ming-Hsun Tsai wrote:
> Hi all:
>
> I setup a new server to replace my old server and migrate all MySQL data
> from old server to new server but new server has new version of horde
> included turba 2.3.1. after all things done. I can't see my address book.
> Please help.
>
> Following is my step. hope it would help.
>
> 1.run 2.1_to_2.2_add_sql_share_tables.sql and
> convert_datatree_shares_to_sql.php without errors.
> 2.export mysql data from old server to new server.
> 3.login to new server. check for address book. only showed the global shared
> address book. the personal address book gone.....
> 4.I found some account can read its address book with
> [attribute_params]='a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:5:"aaaaa";}'
> 5.I tried to create personal address book for the user which can't read its
> personal address book. to check if the address book created all contacts
> back. but failed. and I found the [attribute_params] in this account is like
> this
> 'a:3:{s:6:"source";s:8:"localsql";s:4:"name";s:32:"7b7b3ecea5a9d1c591a40e83067d29c8";s:7:"default";b:0;}'
> 6.I try to update the [attribute_params] from
> 'a:3:{s:6:"source";s:8:"localsql";s:4:"name";s:32:"7b7b3ecea5a9d1c591a40e83067d29c8";s:7:"default";b:0;}'
> to
> 'a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:4:"bakk";}'
> and the contact for that user bakk comes back.
> 7.so I update all users attribute_params to
> 'a:3:{s:6:"source";s:8:"localsql";s:7:"default";b:1;s:4:"name";s:5:"aaaaa";}'.
> to see if it works. but failed.