Forum .LRN Q&A: notes on upgrading dotLRN to 2.2.0a1

How did you circumwent the problem that new portal upgrade destroys the community portals? At least in none of our tested upgrades we were able to access a community portal anymore and all community portals just showed the user portal.

So we upgraded acs-core without the new-portal or dotlrn part and things a working just fine :)

We post a fix for news-aggregator bug (number)#2710, may be tomorow we finish the corrections to other problems.

Malte,

We are working on documenting the upgrade process from 2.1.3 (tarball) to 2.2.0a1 (cvs oacs-5-2) as part of E-lane developments. The upgrade was fine, just few patches was generated, but we need carry out some tests on packages from dotlrn-all and few others from dotlrn-extras. This week we will finish this work. I am just waiting a final report from my team to produce a more detailed

I contacted Rodrigo Proença about your report and we could see in our upgrade class portals were available after upgrade and we had no problems acessing its objects. As i said we are working on dotlrn 2.1.3 test install. We created objects (departaments, classes, portals) on it and upgrade to 2.2.0a1. Is it possible to you send a database backup from your original 2.1.3 system you are trying to upgrade?

the portal_source__set_def_param problem was due to the fact that at one point in time (at least in our installation) the SQL procedure did not insert into the portal_def_params table, but into the portal_params table.

This screwed up any new installations of portlets, like news-aggregator and weblogger. So it might be only specific to our system, but people should be aware of it (maybe you could quickly scan that for each datasource-key (or whatever the name) in portal_params there must be an entry in portal_def_params ?

<h1>Report of upgrade from 2.1.3 to 2.2</h1>

Hi all,
we just upgraded our test system from 2.1.3 to oacs5-2 with .LRN 2.2.0a2.
<h2>Upgrade Problems</h2>

Here the problemes we faced during upgrade:

• For some reason upgrade of file-storage, content-repository and dotlrn were always hanging. Also the after upgrade callback of news resulted to an error saying that we have a duplicate value for the service contract in our database.
• fter several runs file-storage went through. What was hanging was the update calls at the end of file-storage/sql/postgresql/upgrade/upgrade-5.1.0a16-5.1.0a17.sql
• dotlrn upgrade stopped after running the sql/postgresql/upgrade/upgrade-2.1.3-2.2.0d1.sql script. So I assume dotlrn::apm::after_upgrade has not been called. But I need to check that. APM at least is displaying version 2.2.0a2.
• Regarding content repository it turned out that the temporary function __tmp_crnewtree() in upgrade-5.2.0b2-5.2.0b3.sql was the reason why upgrade hanging. We found out accidently after 20 minutes that the upgrade continued.

<h2>Testing the site</h2>

Here a first report testing after the upgrade:
<h4>Static Portlet</h4>

• For some reason all static portlets have an error because a column body is expended but we have a column content inside our database. No idea where that is coming from.

  select body, pretty_name, format from static_portal_content where content_id = xyz

• Creating a new static portlet therefore fails

<h4>Classes, Communities, Subgroups</h4>

• Navigation to classes, courses, subgroups and communities work
• Creating subgroups fails:

  Database operation "dml" failed (exception ERROR, "FEHLER:  Einfügen oder Aktualisieren in Tabelle »acs_objects« verletzt Fremdschlüssel-Constraint »acs_objects_package_id_fk«
  DETAIL:  Schlüssel (package_id)=(0) ist nicht in Tabelle »apm_packages« vorhanden.
  ")
  FEHLER:  Einfügen oder Aktualisieren in Tabelle »acs_objects« verletzt Fremdschlüssel-Constraint »acs_objects_package_id_fk«
  DETAIL:  Schlüssel (package_id)=(0) ist nicht in Tabelle »apm_packages« vorhanden.
  SQL:
              update acs_objects
              set package_id = '0'
              where object_id = '2238349'

• Copying a group fails

  Database operation "dml" failed (exception ERROR, "FEHLER:  Einfügen oder Aktualisieren in Tabelle »acs_objects« verletzt Fremdschlüssel-Constraint »acs_objects_package_id_fk«
  DETAIL:  Schlüssel (package_id)=(0) ist nicht in Tabelle »apm_packages« vorhanden.
  ")
  FEHLER:  Einfügen oder Aktualisieren in Tabelle »acs_objects« verletzt Fremdschlüssel-Constraint »acs_objects_package_id_fk«
  DETAIL:  Schlüssel (package_id)=(0) ist nicht in Tabelle »apm_packages« vorhanden.
  SQL:
              update acs_objects
              set package_id = '0'
              where object_id = '2238641'
  
      while executing
  "ns_pg_bind dml nsdb0 {
              update acs_objects
              set package_id = :object_id
              where object_id = :node_id
          }"

• Archiving a group works
• unarchiving a group works
• Managing members
  • adding a new member works
  • changing role works (slow)
  • removing member works
• Changing portlet name works but
  • For some reason so portlet headers dont shown anymore
  • Simply displaying a page number instead of page name not good
• Changing system template fails:

  expected boolean value but got ""
      while executing
  "if {[parameter::get -package_id $dotlrn_package_id -parameter AdminChangeSiteTemplate_p]} {
  	    set site_template_id [get_site_template_id -community..."
      (procedure "dotlrn_community::get_site_template_id_not_cached" line 5)
      invoked from within
  "dotlrn_community::get_site_template_id_not_cached -community_id 2093034"
      ("eval" body line 1)
      invoked from within
  "eval $script"
  

• Creating welcome message for group works. Wether it is send out, no idea

<h4>Forums</h4>

• Creating a new forum works
• Creating a new thread works works
• Replying a post works
• Move of thread to another thread/forum works
• disabling forums works
• Move to other thread not i18n-ized
• Subscribe others not i18n-ized
• Confirmation of moving to another thread not i18n-ized
• statistics not i18n-ized

Note: We should provide a feature to delete a forum, no?

<h4>FAQ</h4>

• Creating/deleting an FAQ works
• create/delete/preview q&a works
• separte page for each q&a works
• Create form of faq not i18n
• Configure link and configure form not i18n

<h4>Calendar</h4>

• Creating a new item - Javascript to display date selector fails
• Creating an new item works
• Display of items works on all portlets and views
• Deleting an item works
• Editing an item works
• Changing an recurring item is not provided
• Creating a recurring item fails

  Database operation "0or1row" failed (exception NSDB, "Query was not a statement returning rows.")
  FEHLER:  ungültige Eingabesyntax für Typ timestamp with time zone: »12-Mai-2006 0:0«
  SQL:
  select recurrence__new('week',
      	'2',
      	'1 2 4',
      	'12-Mai-2006 0:0',
  	NULL)
  

<h4>Bulk Mail</h4>

• Simply sending a mail worked

<h4>News</h4>

• Creating a new item works
• "Choose an image" not i18n
• "Return to edit" not i18n
• Upload of an image fails ..."Image must be one of the following types:", error text not complete, text not i18n-ized
• return to edit works
• preview works
• confirmation works
• link to administer news on the right not using class button of style sheet
• item displays on porlet

<h4>Survey</h4>

• Creating/deleting a new survey works
• Creating a new question works
• Preview works
• Different display types table, list, sections work
• admin image on the right broken on page survey/one-survey
• processing a survey works
• display of given answers works
• changing a given answer works
• Link on survey portlet "view/edit previous responses" not i18n
• activation/deactivation of survey works
• copy of questions work
• deleting a question works
• moving questions work

<h4>File-Storage</h4>

• File upload works
• new revision works
• delete revision works
• rename works
• copy of files works
• deleting a file works
• moving a file works (slow)
• creating a new folder works (slow)
• moving folder works (slow)
• Parent folder display emtpy if child folder is empty as well (not good)
• deleting a folder works (slow)

/dotlrn/control-panel a valign="top" is missing for the left column with the portlet "Help and Personal Configuration"

Alright,

dotlrn installation fails as soon as the proc apm_parameter_register is called. So some reason the sql query parameter_register never returns.

Looking at the code I have a question. The query text is written directly inside the proc but there is a postgresql.xql where the query is available as well. Which query is in this case executed by the system?

Inside apm-procs.tcl is written

begin
:1 := apm.register_parameter(
parameter_id => :parameter_id,
parameter_name => :parameter_name,
package_key => :package_key,
description => :description,
datatype => :datatype,
default_value => :default_value,
section_name => :section_name,
min_n_values => :min_n_values,
max_n_values => :max_n_values
);
end;

And in the apm-procs-postgresql.xql is written:

select apm__register_parameter(
:parameter_id,
:package_key,
:parameter_name,
:description,
:datatype,
:default_value,
:section_name,
:min_n_values,
:max_n_values
);

The function apm__register_parameter is defined as this:

-- Function: apm__register_parameter(int4, varchar, varchar, varchar, varchar, varchar, varchar, int4, int4)

-- DROP FUNCTION apm__register_parameter(int4, "varchar", "varchar", "varchar", "varchar", "varchar", "varchar", int4, int4);

CREATE OR REPLACE FUNCTION apm__register_parameter(int4, "varchar", "varchar", "varchar", "varchar", "varchar", "varchar", int4, int4)
RETURNS int4 AS
'
declare
register_parameter__parameter_id alias for $1; -- default null
register_parameter__package_key alias for $2;
register_parameter__parameter_name alias for $3;
register_parameter__description alias for $4; -- default null
register_parameter__datatype alias for $5; -- default \'string\'
register_parameter__default_value alias for $6; -- default null
register_parameter__section_name alias for $7; -- default null
register_parameter__min_n_values alias for $8; -- default 1
register_parameter__max_n_values alias for $9; -- default 1

v_parameter_id apm_parameters.parameter_id%TYPE;
cur_val record;
begin
-- Create the new parameter.
v_parameter_id := acs_object__new(
register_parameter__parameter_id,
\'apm_parameter\',
now(),
null,
null,
null,
\'t\',
register_parameter__package_key || \': Parameter \' || register_parameter__parameter_name,
null
);

insert into apm_parameters
(parameter_id, parameter_name, description, package_key, datatype,
default_value, section_name, min_n_values, max_n_values)
values
(v_parameter_id, register_parameter__parameter_name,
register_parameter__description, register_parameter__package_key,
register_parameter__datatype, register_parameter__default_value,
register_parameter__section_name, register_parameter__min_n_values,
register_parameter__max_n_values);

-- Propagate parameter to new instances.
for cur_val in select ap.package_id, p.parameter_id, p.default_value
from apm_parameters p left outer join apm_parameter_values v
using (parameter_id), apm_packages ap
where p.package_key = ap.package_key
and v.attr_value is null
and p.package_key = register_parameter__package_key
loop
PERFORM apm__set_value(
cur_val.parameter_id,
cur_val.package_id,
cur_val.default_value
);
end loop;

return v_parameter_id;

end;'
LANGUAGE 'plpgsql' VOLATILE;

Maybe this is the reason why none of the parameters of the packages are added.

Any idea?

Malte,

Finally we found a way to manage problems due dotlrn parameters (community_level_p, community_type_level_p and dotlrn_level_p) being set to NULL after upgrade.

We tried this solution with recent upgrades we did from dotlrn-2.1.1 to dotlrn-2.2.0a3 and dotlrn-2.1.3 to dotlrn-2.2.0a3, using postgresql

We just create an auxiliary table with sql upgrade script to preserve old parameters values stored in apm_parameter_values and introduced a callback in dotlrn/tcl/apm-callbacks.tcl. This callback is responsible to copy attr_values from auxiliary table to apm_parameter_values after upgrade.

It works for us and upgrade was made easy. Community portals are showed after upgrade and besides not all aplications were fully tested yet we think this solution could be interesting.

We will continue this week looking at dotlrn installations we upgraded searching for bugs or inconvenients after upgrade and testing packages for dotlrn-all. I will post a patch for dotlrn with our suggestion so you could appreciate. Nima, your considerations would be great too.

Patch for bug:

https://openacs.org/bugtracker/openacs/bug?f%5fcomponent=56129&format=table&f%5fstate=7&bug%5fnumber=2717&project%5fid=56106

Hi all,


as I can see there are still two different apm_register_parameter functions defined in acs-kernel:


apm-create.sql:

create or replace function apm__register_parameter (integer,varchar,varchar,varchar,varchar,varchar,varchar,integer,integer)
returns integer as '
declare
  register_parameter__parameter_id           alias for $1;  -- default null
  register_parameter__package_key            alias for $2;
  register_parameter__parameter_name         alias for $3;
  register_parameter__description            alias for $4;  -- default null
  register_parameter__datatype               alias for $5;  -- default ''string''
  register_parameter__default_value          alias for $6;  -- default null
  register_parameter__section_name           alias for $7;  -- default null
  register_parameter__min_n_values           alias for $8;  -- default 1
  register_parameter__max_n_values           alias for $9;  -- default 1

  v_parameter_id         apm_parameters.parameter_id%TYPE;
  v_value_id             apm_parameter_values.value_id%TYPE;
  v_pkg                  record;
begin
    -- Create the new parameter.
    v_parameter_id := acs_object__new(
       register_parameter__parameter_id,
       ''apm_parameter'',
       now(),
       null,
       null,
       null,
       ''t'',
       register_parameter__package_key || '' - '' || register_parameter__parameter_name,
       null
    );

    insert into apm_parameters
    (parameter_id, parameter_name, description, package_key, datatype,
    default_value, section_name, min_n_values, max_n_values)
    values
    (v_parameter_id, register_parameter__parameter_name,
     register_parameter__description, register_parameter__package_key,
     register_parameter__datatype, register_parameter__default_value,
     register_parameter__section_name, register_parameter__min_n_values,
     register_parameter__max_n_values);

    -- Propagate parameter to new instances.
    for v_pkg in
        select package_id
        from apm_packages
        where package_key = register_parameter__package_key
      loop
        v_value_id := apm_parameter_value__new(
            null,
            v_pkg.package_id,
            v_parameter_id,
            register_parameter__default_value
            );
      end loop;

    return v_parameter_id;
end;' language 'plpgsql';

upgrade-5.2.0d1-5.2.0d2.sql:

create or replace function apm__register_parameter (integer,varchar,varchar,varchar,varchar,varchar,varchar,integer,integer)
returns integer as '
declare
  register_parameter__parameter_id           alias for $1;  -- default null
  register_parameter__package_key            alias for $2;
  register_parameter__parameter_name         alias for $3;
  register_parameter__description            alias for $4;  -- default null
  register_parameter__datatype               alias for $5;  -- default ''string''
  register_parameter__default_value          alias for $6;  -- default null
  register_parameter__section_name           alias for $7;  -- default null
  register_parameter__min_n_values           alias for $8;  -- default 1
  register_parameter__max_n_values           alias for $9;  -- default 1

  v_parameter_id         apm_parameters.parameter_id%TYPE;
  cur_val                record;
begin
    -- Create the new parameter.
    v_parameter_id := acs_object__new(
       register_parameter__parameter_id,
       ''apm_parameter'',
       now(),
       null,
       null,
       null,
       ''t'',
       register_parameter__package_key || '': Parameter '' || register_parameter__parameter_name,
       null
    );

    insert into apm_parameters
    (parameter_id, parameter_name, description, package_key, datatype,
    default_value, section_name, min_n_values, max_n_values)
    values
    (v_parameter_id, register_parameter__parameter_name,
     register_parameter__description, register_parameter__package_key,
     register_parameter__datatype, register_parameter__default_value,
     register_parameter__section_name, register_parameter__min_n_values,
     register_parameter__max_n_values);

    -- Propagate parameter to new instances.
    for cur_val in select ap.package_id, p.parameter_id, p.default_value
       from apm_parameters p left outer join apm_parameter_values v
             using (parameter_id), apm_packages ap
      where p.package_key = ap.package_key
        and v.attr_value is null
        and p.package_key = register_parameter__package_key
      loop
        PERFORM apm__set_value(
            cur_val.parameter_id,
            cur_val.package_id,
            cur_val.default_value
            );
      end loop;

    return v_parameter_id;
end;' language 'plpgsql';

Which one is correct? The one in the upgrade skript results to null values. So it is definetly wrong. But what about the other?


Can someone help?

When (at what stage are you creating the new subgroup). Is this after upgrade?

I used the correct function in the create.sql of acs-kernel. Now I can access the communities. But when I try to create a new subgroup or community I get the following exception:

Database operation "dml" failed (exception ERROR, "FEHLER: Einfügen oder Aktualisieren in Tabelle »acs_objects« verletzt Fremdschlüssel-Constraint »acs_objects_package_id_fk«
DETAIL: Schlüssel (package_id)=(0) ist nicht in Tabelle »apm_packages« vorhanden.
")

FEHLER: Einfügen oder Aktualisieren in Tabelle »acs_objects« verletzt Fremdschlüssel-Constraint »acs_objects_package_id_fk«
DETAIL: Schlüssel (package_id)=(0) ist nicht in Tabelle »apm_packages« vorhanden.

SQL:
update acs_objects
set package_id = '0'
where object_id = '3355574'

while executing
"ns_pg_bind dml nsdb0 {
update acs_objects
set package_id = :object_id
where object_id = :node_id
}"
("uplevel" body line 1)
invoked from within
"uplevel $ulevel [list ns_pg_bind $type $db $sql]"
("postgresql" arm line 2)
invoked from within
"switch $driverkey {
oracle {
return [uplevel $ulevel [list ns_ora $type $db $sql] $args]
}
..."
invoked from within
"db_exec dml $db $full_statement_name $sql"
("uplevel" body line 2)
invoked from within
"uplevel 1 $code_block "
invoked from within
"db_with_handle -dbn $dbn db {
db_exec dml $db $full_statement_name $sql
}"
(procedure "db_dml" line 100)
invoked from within
"db_dml update_object_package_id {}"
(procedure "site_node::mount" line 4)
invoked from within
"site_node::mount -node_id $attachments_node_id -object_id [apm_package_id_from_key attachments]"
(procedure "dotlrn_forums::add_applet_to_community" line 14)
invoked from within
"dotlrn_forums::add_applet_to_community $community_id"
(procedure "AcsSc.dotlrn_applet.addapplettocommunity.dotlrn_forums" line 1)
invoked from within
"AcsSc.dotlrn_applet.addapplettocommunity.dotlrn_forums 3355385"
("uplevel" body line 1)
invoked from within
"uplevel $func_and_args"
(procedure "apply" line 3)
invoked from within
"apply $proc_name $arguments"
(procedure "acs_sc_call" line 6)
invoked from within
"acs_sc_call dotlrn_applet $op $list_args $applet_key"
(procedure "applet_call" line 2)
invoked from within
"applet_call $applet_key AddAppletToCommunity [list $community_id]"
invoked from within
"set package_id [applet_call $applet_key AddAppletToCommunity [list $community_id]]"
("uplevel" body line 2)
invoked from within
"uplevel 1 $transaction_code "
(procedure "db_transaction" line 1)
invoked from within
"db_transaction {
set package_id [applet_call $applet_key AddAppletToCommunity [list $community_id]]

register_a..."
(procedure "dotlrn_community::add_applet_to_community" line 2)
invoked from within
"dotlrn_community::add_applet_to_community $community_id $applet_key"
("foreach" body line 3)
invoked from within
"foreach applet_key $default_applets_list {
if {[dotlrn_applet::applet_exists_p -applet_key $applet_key]} {
dotlrn_..."
("uplevel" body line 68)
invoked from within
"uplevel 1 $transaction_code "
(procedure "db_transaction" line 39)
invoked from within
"db_transaction {
set user_id [ad_conn user_id]
set community_id [package_instantiate_object -extra_vars $extra_vars $object_ty..."
(procedure "dotlrn_community::new" line 26)
invoked from within
"dotlrn_community::new -parent_community_id $parent_community_id -description $description -community_type dotlrn_community -pretty_name $pretty_na..."
invoked from within
"set subcomm_id [dotlrn_community::new -parent_community_id $parent_community_id -description $description -community_type dotlrn_community -pretty..."
("uplevel" body line 2)
invoked from within
"uplevel 1 $transaction_code "
(procedure "db_transaction" line 39)
invoked from within
"db_transaction {
set subcomm_id [dotlrn_community::new -parent_community_id $parent_community_id -description $description -community_type ..."
invoked from within
"if {[form is_valid add_subcomm]} {
form get_values add_subcomm pretty_name description join_policy referer

# we set some extra vars based on..."
("uplevel" body line 57)
invoked from within
"uplevel {
#
# Copyright (C) 2001, 2002 MIT
#
# This file is part of dotLRN.
#
# dotLRN is free software; you can redistribute it and/or modify it u..."
(procedure "code::tcl::/www/unima0/packages/dotlrn/www/subcommunity-new" line 2)
invoked from within
"code::tcl::$__adp_stub"
invoked from within
"if { [file exists $__adp_stub.tcl] } {

# ensure that data source preparation procedure exists and is up-to-date
adp_init tcl $__adp_stub
..."
("uplevel" body line 3)
invoked from within
"uplevel {

if { [file exists $__adp_stub.tcl] } {

# ensure that data source preparation procedure exists and is up-to-date
adp_init t..."
(procedure "adp_prepare" line 2)
invoked from within
"adp_prepare "
(procedure "template::adp_parse" line 30)
invoked from within
"template::adp_parse [file root [ad_conn file]] {}"
(procedure "adp_parse_ad_conn_file" line 5)
invoked from within
"$handler"
("uplevel" body line 2)
invoked from within
"uplevel $code"
invoked from within
"ad_try {
$handler
} ad_script_abort val {
# do nothing
}"
invoked from within
"rp_serve_concrete_file [ad_conn file]"
(procedure "rp_serve_abstract_file" line 60)
invoked from within
"rp_serve_abstract_file "$root/$path""
("uplevel" body line 2)
invoked from within
"uplevel $code"
invoked from within
"ad_try {
rp_serve_abstract_file "$root/$path"
set tcl_url2file([ad_conn url]) [ad_conn file]
set tcl_url2path_info..."

I turned on ds and tried again with db on. here the db stack around the relevant part:

dbqd.acs-tcl.tcl.apm-procs.apm_package_registered_p.apm_package_registered_p: 0or1row nsdb0
select 1 from apm_package_types
where package_key = 'attachments'

2 ms 0or1row dbqd.dotlrn.tcl.community-procs.dotlrn_community::applet_active_p.select_active_applet_p: 0or1row nsdb0
select 1
from dotlrn_community_applets,
dotlrn_applets
where dotlrn_community_applets.community_id = '3355576'
and dotlrn_community_applets.applet_id = dotlrn_applets.applet_id
and dotlrn_applets.applet_key = 'dotlrn_fs'
and dotlrn_community_applets.active_p = 't'
and dotlrn_applets.active_p = 't'

2 ms 0or1row dbqd.acs-subsite.tcl.package-procs.package_instantiate_object.package_select: 0or1row nsdb0

select t.package_name
from acs_object_types t
where t.object_type = 'site_node'

6 ms 0or1row dbqd.acs-subsite.tcl.package-procs.package_instantiate_object.create_object: 0or1row nsdb0

select site_node__new(NULL,'3355756',null,NULL,'t','t','27685','134.155.48.12')

2 ms select dbqd.acs-subsite.tcl.subsite-callback-procs.subsite_callback.select_callbacks: select nsdb0

select distinct callback, callback_type
from subsite_callbacks
where object_type in (select t2.object_type
from acs_object_types t1, acs_object_types t2
where t2.tree_sortkey <= t1.tree_sortkey
and t1.tree_sortkey between t2.tree_sortkey and tree_right(t2.tree_sortkey)
and t1.object_type = 'site_node')
and event_type = 'insert'

2 ms dml dbqd.acs-tcl.tcl.site-nodes-procs.site_node::mount.mount_object: dml nsdb0
update site_nodes
set object_id = '0'
where node_id = '3355765'

3 ms dml dbqd.acs-tcl.tcl.site-nodes-procs.site_node::mount.update_object_package_id: dml nsdb0
update acs_objects
set package_id = :object_id
where object_id = :node_id

I don't think this has something todo with this problem here but the after-upgrade service contract of the news packages breaks during upgrade:

news::install::after_upgrade -from_version_name 5.0d7 -to_version_name 5.2.0d6

Try this from the ds/shell

[apm_package_id_from_key attachments]

and see what it returns. It apparently is returning 0 which seems wrong unless attachements isn't installed or someting.

Not being able to accesss a community is fixed when using the function defined in the acs-kernel-create.sql instead of that in the upgrade script.

Now to the attachments issue.

Ok. from what I see during the upgrade I should have permitted the apm to create an attachments instance under /attachments. Since I had attachments installed but no instance of it the new dependency of forums broke the creation and cloning of communities. The problem is, that apm always recommends you to create an instance of some packages under /. Normally you don't need to do that because its not necessary, right? But not in this case.

After creating an instance I got an new error message when creating a community: CommDefaultSiteTemplate_p parameter of dotlrn was missing which should have been installed after upgrade of dotlrn package. I tried to do that manually and it took at least 5 min to create the parameter with apm. I guess this must have been the case during upgrade and a server restart caused this to remain unfinished.

After adding the parameter manually the creation of communties works again.

Now my question is: I would like to make another clean upgrade for a last time before I start checking all the common functionalities of dotlrn. So far I have been using the tarball .LRN 2.2.0 Final. What shall I use this time? HEAD, oacs-5-2 branch?

Greetings,
Nima

Malte: its apm__register_parameter

Nima,

Did you try the upgrade? Did you have any problem with it? Please, give us feedback on this to include posible issue in the agenda of .lrn meeting.

Alright. We have finished our upgrade and merging work and will commit all our fixes in 1-2 hours.