Hello there,
For the past couple of days, Rafael Calvo and myself have been trying to figure out a way to upgrade to 4.6 without having to start from scratch.
So we would like to get your advise on what we have done and see if you guys can think of problems we might encounter later on by doing an upgrade this web.
So here we go:
First, what we did was to do a CVS checkout of release 4.6 for the acs-core:
nsadmin@server-name:/web> cvs -z3 -d :pserver:anonymous@openacs.org:/cvsroot checkout -roacs-4-6 acs-core
Then we checked for all the new SQL scripts (we are doing it for Postgres only) on this new version and here is the list of them:
-- ACS Kernel 4.5 : Files
./acs-kernel/sql/postgresql/site-node-object-map-create.sql
./acs-kernel/sql/postgresql/upgrade/upgrade-4.5-4.5.1.sql
./acs-kernel/sql/postgresql/upgrade/upgrade-4.5.1-4.6.sql
-- ACS Content Repository 4.5
./acs-content-repository/sql/postgresql/upgrade/upgrade-4.5-4.6.sql
-- ACS Mail 4.5
./acs-mail/sql/postgresql/upgrade/upgrade-4.5-4.6.sql
-- ACS Service Contract 4.5 ./acs-service-contract/sql/postgresql/upgrade/upgrade-4.5.1-4.6.sql
-- ACS Subsite 4.5
./acs-subsite/sql/postgresql/upgrade/upgrade-4.5-4.5.1.sql
./acs-subsite/sql/postgresql/user-sc-create.sql
-- Search 4.5
./search/sql/postgresql/upgrade/upgrade-4.5-4.5.1.sql
we updated the data model by running this scripts.
The core seemed to work
then we did the same for otrher packages: file-storage, and we got an error... so we tried to drop it, but of course the data model had been updated so the drop script tried to use unnexistent functions, so we can not drop it.
Has anyone ported successfull a 4.5 site to 4.6? on postgres?
If not, and if we can live without keeping the packages (not much on the old bboads, file-storage..) but I do not want to
have the 100+ users having to register again, what can we do?
Is there a way of taking user names and p[asswords to another system? would copying the user table work? what happens with parties and so on?
Any help would be appreciated.
