Hi Malte,
good news. I think we guessed what was wrong in the upgrade and we are going to fix it in a better way.
Community and Class portals were not destroyed by upgrade. Some parameters - dotlrn_level_p, community_level_p and community_type_level_p - were changed to null (we really dont know why yet) in the upgrade. Maybe apm reset all them to null?? We are trying to see how could be happen...
Just go into your class or community package instance and change this parameters in site-map setting them as they were configured originally on community or class creation:
ad_parameter -package_id $package_id -set 0 dotlrn_level_p
ad_parameter -package_id $package_id -set 0 community_type_level_p
ad_parameter -package_id $package_id -set 1 community_level_p
Here we go... your portal is up!
Second problem:
we had undefined config(package_id) for some new applets as curriculum and news-agregator. I tryed just drop actual portlet implementation, change portal_datasource__set_def_param value for package_id from "" to "list" and load implementation again.
After that go into your portlet procedures and add the switch
-extra_params [list package_id $package_id]
where you declare the call to proc
portal::add_element_parameters and portal::remove_element_parameters
It worked
We are preparing changes to do on upgrade.
If the community could make some advices on how to solve it it will be very appreciated
Thank you
\Orzenil
