[turba] problem of upgrade turba from 2.1.7 to 2.2

[David Chang]

Quoting David Chang <david at tmv.gov.tw>:

> Quoting Michael Rubinsky <mrubinsk at horde.org>:
>
>> Quoting David Chang <david at tmv.gov.tw>:
>>
>>> Quoting Michael Rubinsky <mrubinsk at horde.org>:
>>>
>>>> Quoting David Chang <david at tmv.gov.tw>:
>>>>
>>>>> After upgrade localsql backend from 2.1.7 to 2.2,some of prefences did
>>>>> not work/map successfully,eg.
>>>>> imp[search_source],imp[search_fields],turba[addressbooks]. For
>>>>> example, after run done 2007-06-17_flatten_shares.php ,and login to
>>>>> horde-3.2,the imp[search_source] preference looks like this:
>>>>> pref_uid  pref_scope  pref_name    pref_value
>>>>> ========  ==========  =========    ==========
>>>>> user_a    turba       addressbooks localsql
>>>>>                                  local_ldap
>>>>>                                    
>>>>> localsql:dd38b1b284f79796351d0c5fda5fd80f
>>>>>                                    
>>>>> localsql:55dae36c62c8e10ef9583cf522299ff1
>>>>>
>>>>> However,as i know,if it work ,that should be,
>>>>> pref_uid  pref_scope  pref_name    pref_value
>>>>> ========  ==========  =========    ==========
>>>>> user_a    turba       addressbooks user_a
>>>>>                                  local_ldap
>>>>>                                  dd38b1b284f79796351d0c5fda5fd80f
>>>>>                                  55dae36c62c8e10ef9583cf522299ff1
>>>>>
>>>>> FYI,here are the turba's conf.php :
>>>>> $conf['client']['addressbook'] = 'localsql';
>>>>> $conf['shares']['source'] = 'localsql';
>>>>>
>>>>> What else am i miss in the upgrade step ?
>>>>
>>>> Those values *should* be updated transparently as each user logs in
>>>> for the first time after the upgrade.  Since it's a preference
>>>> setting, and some preference backends would require a
>>>> username/password for each user we are modifying it was impossible to
>>>> perform this part of the upgrade from a command line script.  Try
>>>> having one of the user login and access turba/imp and then check the
>>>> value of those prefs.
>>>
>>>>
>>>> Thanks,
>>>> mike
>>>>
>>>> --
>>>> The Horde Project (www.horde.org)
>>>> mrubinsk at horde.org
>>>>
>>>> "Time just hates me. That's why it made me an adult." - Josh Joplin
>>>
>>> Hello michael,
>>> Actually,those preference i report,was the value since user_a first
>>>   time login to horde-3.2. That is transparent update did not
>>> happen   for these preference. It only work once,if i delete these
>>> preference  manualy after upgrade completed,and then user_a login
>>> to horde-3.2 .
>>
>>
>> Can you look and see if there is an entry in user_a's prefs for the
>> turba-maintenance_tasks pref?
>>
>>
>>
>>
>> Thanks,
>> mike
>>
>> --
>> The Horde Project (www.horde.org)
>> mrubinsk at horde.org
>>
>> "Time just hates me. That's why it made me an adult." - Josh Joplin
> Hello mike:
> Yes,there is
> a:2:{i:0;s:12:"upgradeprefs";i:1;s:12:"upgradelists";}
>
> Thanks,
> david
>
> --
> 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
>
Hello mike,
Do you mind if i create it to ticket system ?

David