[horde] Portal blocks and some other prefs not migrated

[Jan Schneider]

Zitat von Stephan Kleber <stephan at admin.nabira.de>:

> Am 09.05.2011 11:07, schrieb Jan Schneider:
>>
>> Zitat von Stephan Kleber <stephan at admin.nabira.de>:
>>
>>> Hi,
>>>
>>> after some tests I wanted to migrate Horde3 to Horde4 (4.0.2 from PEAR).
>>>
>>> On the first test the portal looked as it did in Horde3, which is as
>>> expected.
>>>
>>> On my second test I created a new copy of the Horde3 database which I
>>> converted to Horde4 formats once by the WebGui-System and once by
>>> command-line script.
>>>
>>> In both cases the Portal is scrambled. On each position of a portal
>>> block there is just displayed the heading "Error" and the content "not
>>> found." Horde log shows several of the following, each for one portal
>>> block:
>>>
>>> 2011-05-08T15:10:25+02:00 NOTICE: HORDE [horde] PHP ERROR: Undefined
>>> index:  type2 [pid 15648 on line 83 of
>>> "/usr/share/php/Horde/Core/Block/Layout/View.php"]
>>> 2011-05-08T15:10:25+02:00 NOTICE: HORDE [horde] PHP ERROR: Undefined
>>> index:  type2 [pid 15648 on line 46 of
>>> "/usr/share/php/Horde/Core/Block/Layout.php"]
>>>
>>> The corresponding entries in the horde_prefs database table look fine,
>>> as far as I can tell:
>>>
>>> 'stephan at admin.nabira.de', 'horde', 'portal_layout',
>>> 'a:6:{i:0;a:4:{i:0;a:4:{s:3:"app";s:5:"horde";s:6:"height";i:1;s:5:"width";i:1;s:6:"params";a:2:{s:4:"type";s:7:"sunrise";s:6:"params";a:2:{s:10:"__location";s:7:"Germany";s:8:"location";s:12:"48.217:9.917";}}}i:1;a:4:{s:3:"app";s:9:"kronolith";s:6:"params";a:2:{s:4:"type";s:7:"summary";s:6:"params";a:2:{s:8:"calendar";s:5:"__all";s:9:"maxevents";s:2:"15";}}s:6:"height";i:3;s:5:"width";i:3;}i:2;s:7:"covered";i:3;s:7:"covered";}i:1;a:4:{i:0;a:4:{s:3:"app";s:5:"horde";s:6:"height";i:1;s:5:"width";i:1;s:6:"params";a:2:{s:4:"type";s:4:"moon";s:6:"params";a:2:{s:5:"phase";s:7:"current";s:10:"hemisphere";s:8:"northern";}}}i:1;s:7:"covered";i:2;s:7:"covered";i:3;s:7:"covered";}i:2;a:4:{i:0;a:4:{s:3:"app";s:3:"imp";s:6:"params";a:2:{s:4:"type";s:7:"summary";s:6:"params";b:0;}s:6:"height";i:2;s:5:"width";i:1;}i:1;s:7:"covered";i:2;s:7:"covered";i:3;s:7:"covered";}i:3;a:4:{i:0;s:7:"covered";i:1;a:4:{s:3:"app";s:3:"nag";s:6:"params";a:2:{s:4:"type";s:7:"summary";s:6:"params";a:9:{s:
> 11
>>>
>> :
>>> "block_title";s:8:"Aufgaben";s:8:"show_pri";s:2:"on";s:12:"show_actions";s:2:"on";s:8:"show_due";s:2:"on";s:13:"show_tasklist";s:2:"on";s:11:"show_alarms";s:2:"on";s:13:"show_category";s:2:"on";s:12:"show_overdue";s:2:"on";s:14:"show_tasklists";a:1:{i:0;s:23:"stephan at admin.nabira.de";}}}s:6:"height";i:3;s:5:"width";i:3;}i:2;s:7:"covered";i:3;s:7:"covered";}i:4;a:4:{i:0;a:4:{s:3:"app";s:5:"turba";s:6:"params";a:2:{s:4:"type";s:10:"minisearch";s:6:"params";a:0:{}}s:6:"height";i:2;s:5:"width";i:1;}i:1;s:7:"covered";i:2;s:7:"covered";i:3;s:7:"covered";}i:5;a:4:{i:0;s:7:"covered";i:1;s:7:"covered";i:2;s:7:"covered";i:3;s:7:"covered";}}'
>>>
>>>
>>> When I manually configure a new portal block, this one is shown
>>> correctly even if it is the same type as the one not migrated
>>> sucessfully.
>>>
>>> Any ideas?
>>>
>>>
>>>
>>> Other Prefs that weren't migrated correctly are the alternate identities
>>> of users. I did not find anything special about this in the logs. The
>>> database seems to reflect the old settings correctly and adding a new
>>> identity works fine but the old ones are missing either way.
>>
>> Preference migration happens as part of the login process. You are
>> probably testing with a user that already logged in to Horde 4 *before*
>> you copied the Horde 3 preferences.
>>
>> Jan.
>>
>
> Again, I dropped all my Horde4 database tables and imported my Horde3
> database dump. No login was logged in the meantime.
>
> Besides one admin account, that indeed logged in before the "upgrade
> database" step in the administrative configuration, I tested with three
> non-admin accounts, that definitely never were used to log in since
> import or upgrade of the Horde3 database. Each with the same problem.
>
> I realized that my first tests were done in Horde 4.0.1 and the import,
> since which I noticed the problem, was done in Horde 4.0.2.
> Has something been changed between the two releases, that could have
> broken this?

I don't think so.

> You raised a suspicion in me, that it may have something to do with the
> authentication mechanism/backend. Normally I use IMAP (have already done
> in Horde3) but I have tested it with sql, too. Same result.
>
> I'm especially confused since it was working perfectly on several tests
> I did before (with 4.0.1).

Check the contents of the upgrade_tasks preference before and after  
the first log in.

Jan.

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