Forum .LRN Q&A: How upgrade from rc1 to 2.0.1

Collapse
Posted by Nima Mazloumi on
That's true for OpenACS packages but what about dotLRN packages? Are they also recognized by the Installer?

At least non of them is offered as an upgrade.

Also how do I upgrade the language catalogs. They are also not recognized by the Installer.

I would like to use the tarball 2.0.1 but what do I do here? Do I simply extract it over my rc1 installation?

What happens if the datamodel changed?

Greetings,
Nima

Collapse
Posted by Joel Aufrecht on
I forgot to update the package info for the dotlrn packages when I made 2.0.1, so the installer doesn't recognize that there's new stuff.  This will be corrected in 2.0.2, which is due this week.

"Also how do I upgrade the language catalogs. They are also not recognized by the Installer."

At the very end of https://openacs.org/doc/openacs-HEAD/upgrade-openacs.html:
'If you are using locales other than en_US, go to acs-lang/admin and "Import all Messages" to load the new translated messages. Your local translations, if any, will take precedence over imported translations.'

This will work for anything that got installed - ie, it will work for 5.0.3, but not for .LRN right now because of the problem with 2.0.1 detailed above.  The workaround for .LRN is to get the tarball.

"I would like to use the tarball 2.0.1 but what do I do here? Do I simply extract it over my rc1 installation?"
Yes.  If you have local custom work, it's more complicated.  But basically, you update the file system and then you run the Installer from the web page. Both scenarios are described here:
https://openacs.org/doc/openacs-HEAD/upgrade-openacs-files.html.  If you do "Upgrade from repository" then all of this happens automatically.

"What happens if the datamodel changed?"
If the data model changed between 2.0.1 and 2.0.2 (for example), the installer will run all necessary upgrade scripts.  If you have customized your data model, then that's pretty complicated.