Hi,
I've been using 8.0.3 for some time - now I'd love to try 0.8.5 - preferably with the data from my previous installation.
Is that possible? How?
can I just put the database in the new config.-file or is there way to just upgrade with subversion?
thanks a lot
Hein
Please backup everything! The database format is no different, so theoretically you should just be able to upload the new files over the old, careful to preserve your config file. I don't suggest doing this on a production installation. Perhaps you could make a copy of your production installation in a different directory, make a copy the database and point to the copy, make sure everything is working, then upgrade the copy. It would be nice if you could report back your results as I don't think anyone has tried this yet. This is exactly the type of testing that needs done so we can develop an upgrade procedure before considering making a final release.
Cheers,
Jon
so, all I did was I fully installed 8.5 in a different directory, run setup and then changed the variables in the config.php.
so far no bugs I'm aware off. all smooth and moving.
cheers
hein
Hi,
I did following:
1. zip'ed all files in my current 0.8.3 installation from the local server installation.
2. Unzipped the new 0.8.5-beta so all files in the 0.8.3 directory where overwritten with the files from 0.8.5-beta, and new files just added.
3. reloaded by installation directory in the browser and got following error: "ProjectPier is not installed. Please redirect your browser to public/install folder and follow installation procedure"
4. the reason was that the config.php was overwritten. So I took the 0.8.3 config.php (which I had backed up before) and copied to the config directory.
5. I edited the now restored 0.8.3 config.php file in following way:
define('PRODUCT_VERSION', '0.8.5.0') was updated to reflect the new version number.
It seems to be running without problems after this.
When doing an upgrade some config data needs to extracted from the old config file and added to the new one, or the old is just reused and version number is updated. This only works if no new items are in the config.php, otherwise a kind of merge is needed.
The problem with the "copy over approach" is that the user can only roll back if a backup was taken (and of course he/she will do that). But sometimes it could also be good to have both version running so you install in a new location and update the config.php to the same entries as in the old installation, and then you also make sure that non-official themes are copied from the old installation to the new location, and that the theme from the old installation is selected automatically (so the user does not see a "new design" after upgrade).
There could also be a problem with the file storage setting. Default it is set to database, but the user might have selected file storage instead. So in general an upgrade should preserve all configuration settings in the system and select default for new ones.
br,
astradss
P.S. I also tried the parallel installation and the change the new config.php file to reflect the data base setting in the old file, and also update the version number. After this a special theme where copied to the new installation. This also works fine for me.