Forum .LRN Q&A: Re: .LRN 2.0.3 just needs to be tested

Collapse
Posted by Joel Aufrecht on
https://openacs.org/doc/openacs-HEAD/upgrade-overview.html

Basically, if you have no custom code it's simple.  If you have custom code, then you have to go through whatever process you use to update the files, but after that it's still simple.

Don't upgrade to .LRN 2.0.2, because there's an upgrade bug in the dotlrn package itself.  Wait for 2.0.3.  And, of course, always test even the safest upgrades on a copy of the production db first, and always make backups.

Collapse
Posted by Martin Magerl on
Hi,

here are my first test results:

a) Homework-portlet:
- cr_type_relations are only added, when upgrading from 2.0.2 to 2.0.3:
I've upgraded from 2.0.1 and APM did not run "upgrade-2.0.2-2.0.3.sql".
Therefore I had to add content repository type "homework_corretion" manually.

- version-add.tcl:
When trying to upload a new version of a file (version-add.tcl), homework_file_id is null, which results in an error message.
Maybe, this could be fixed in two ways:
- Move call of dotlrn_homework::new after check of
homework_file_p and add "set homework_file_id 0" in
corresponding else clause
- check, if homework_file_id exsists_and_not_null,
before calling dotlrn_homework::new
- move call of dotlrn_homework::new into if/else-
statement and change call in else clause

- download links in folder-chunk.tcl, used in dotlrn-homework-portlet in class home and homework-folde:
Using variable "title" in download-links (like in file.tcl) seems not to work. Unfortunately I don't know why! Same call in file.tcl (using file-postgres.xql) works.

- Show all versions:
When showing all versions, download of each file points to location of oldest version.
This is caused by a missing "version." in variable "@download_url@" used in multirow

- notifications:
Notifications messages like on new comments included some source code like characters. E.g.:
Message key "dotlrn-homework.lt_admin_has_uploaded" contains text
"notification::new -type_id [notification::type::get_type_id -short_name correction_upload] \ -object_id $homework_file_id -response_id $homework_file_id -notif_subject "<#lt_correction_file_al Correction file alert"

- context-bar:
Context-bar includes an untranslated "<span>#</span>dotlrn.classes_pretty_plural#"
I think, this problem is not related in dotlrn-homework

b) Creating "Limited Access (Guest) Users":
Works fine! Thanks!

c) file-storage:
works fine!

---< additional information on building test server >---

Enviroment:
===========
- AOLserver/3.3.1+ad13
- Postgres 7.3.4

"Clean" install of dotlrn 2.0.1:
=======================================

- create database dotlrn20
- download tarball 2.0.1 and extract to /web/dotlrn20
- chown to dotlrn20.web and chmod -R g+w /web/dotlrn20
- copy own config.tcl and certs to /web/dotlrn20/etc
- start aolserver parameters with -t config.tcl -u dotlrn20 -g web
- start installation via web frontend
- loOK into error.log => no errors reported
- delete log (better overview)
- restart server after "automatic" shutdown
- log in and add me as professor to dotlrn (full access, no guest)
- create department "Medizinische Informatik"
- create subject "Praktische Informatik" in department
- create term "SS 2004"
- create class "GPI 1" with term "SS 2004" and Subject "Praktische Informatik"
- created test student and added him to class "GPI 1" (full access, no guest)
- stop server
- pg_dump-backup of dotlrn 2.0.1 database
- restart server
- loOK into error.log => no errors reported

Upgrading to dotlrn 2.0.3:
==========================

- pg_dump-backup of dotlrn 2.0.1 database
- download and unzip dotlrn 2.0.3
- "cp -r" dotlrn 2.0.3 files to /web/dotlrn20
- chown to dotlrn20.web and chmod -R g+w /web/dotlrn20
- replace config.tcl by own config.tcl again
- Upgrade system using "Upgrade system from local filesystem"
- Select all application/services and start upgrading
- Click on restart server => server shutdown
- Restart server manually (I have not installed daemontools for testserver)
- After restart: look into error.log => no errors reported