upgrade path, backup and restore questions
Posted: Wed Apr 23, 2008 8:15 pm
Hi all,
I'm working on a production site running CMSMS v1.0.2 Maui. I know this version is considered totally ancient and obsolete.
I did not set up the original CMSMS installation or site, but am now tasked with upgrading the CMS and improving the overall site.
About upgrading, I've researched this forum quite a bit, and have a few questions.
::1:: I would like to go straight from 1.0.2 to 1.2.4. I have backups of the files and sql db (using MySQL Administrator).
I've read posts and docs suggesting going 1.0.2-->1.2.4 is an acceptable method, BUT I've also seen several posts by Pierre M. saying upgrade should be 1.0.2-->1.1-->1.2.4. Pierre mentions changes in the module API for doing this upgrade path.
There are several modules installed in this site, including FeedbackForm v 0.9.14, Album 0.7.4, CMSMailer 1.73.10, and MenuManager 1.2. These particular modules are used heavily in the site. There are about 8 others also installed.
I really don't want any of these modules to break because of an upgrade (of course I don't want anything to break
. Are modules upgraded automatically with everything else?
There is a note in the installation docs about Feedback Form 0.9.14:
"The FeedbackForms module is incompatible with 1.0 (fatal errors in admin area) before version 0.9.14, and you can't install that version prior to 1.0, so uninstall it before doing an upgrade to 1.0."
(Does this note mean I don't have to worry about FeedbackForm 0.9.14 because I've already got v 1.0.2?)
Question: What would be the best, safest and most straighforward upgrade method given my situation? I can upgrade modules later if necessary, but the CMSMS overall upgrade is important to get right first.
::2:: If something does go wrong, what is the correct restore method? Simply copy back the files, and run a restore operation with the backup sql file?
I would need to restore the old site ASAP if anything at all goes wrong during the upgrade. Absolutely minimal downtime is required.
::3:: Are there any very common problems that come up with upgrades like this? Any customized templates, CSS, etc, that can cause problems?
Thanks in advance for any help!
~Doug
I'm working on a production site running CMSMS v1.0.2 Maui. I know this version is considered totally ancient and obsolete.
I did not set up the original CMSMS installation or site, but am now tasked with upgrading the CMS and improving the overall site.
About upgrading, I've researched this forum quite a bit, and have a few questions.
::1:: I would like to go straight from 1.0.2 to 1.2.4. I have backups of the files and sql db (using MySQL Administrator).
I've read posts and docs suggesting going 1.0.2-->1.2.4 is an acceptable method, BUT I've also seen several posts by Pierre M. saying upgrade should be 1.0.2-->1.1-->1.2.4. Pierre mentions changes in the module API for doing this upgrade path.
There are several modules installed in this site, including FeedbackForm v 0.9.14, Album 0.7.4, CMSMailer 1.73.10, and MenuManager 1.2. These particular modules are used heavily in the site. There are about 8 others also installed.
I really don't want any of these modules to break because of an upgrade (of course I don't want anything to break

There is a note in the installation docs about Feedback Form 0.9.14:
"The FeedbackForms module is incompatible with 1.0 (fatal errors in admin area) before version 0.9.14, and you can't install that version prior to 1.0, so uninstall it before doing an upgrade to 1.0."
(Does this note mean I don't have to worry about FeedbackForm 0.9.14 because I've already got v 1.0.2?)
Question: What would be the best, safest and most straighforward upgrade method given my situation? I can upgrade modules later if necessary, but the CMSMS overall upgrade is important to get right first.
::2:: If something does go wrong, what is the correct restore method? Simply copy back the files, and run a restore operation with the backup sql file?
I would need to restore the old site ASAP if anything at all goes wrong during the upgrade. Absolutely minimal downtime is required.
::3:: Are there any very common problems that come up with upgrades like this? Any customized templates, CSS, etc, that can cause problems?
Thanks in advance for any help!
~Doug