upgrade path, backup and restore questions

[doug_n]

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

[doug_n]

Anybody? 

Any help is greatly appreciated!

There is conflicting info on this forum, from different Support Team Members, about these issues. 

It would be great, and *extremely* helpful, to get this straight. 

I'm in the unfortunate position of having to take over maintenance on a busy production site from someone who never bothered to upgrade, and loaded it up with modules.

To simplify my post: 

1. How best and safest to upgrade from 1.0.2-->1.2.4 ?
2. What's the fastest recovery method if something goes wrong ?
3. What are the most common problems with upgrades like this ?

If this looks too risky overall, I may just have to rebuild the site with v 1.2.4 completely from scratch.  But I'd like to avoid that if possible.

Many thanks in advance!

~Doug

[alby]

I'm in the unfortunate position of having to take over maintenance on a busy production site from someone who never bothered to upgrade, and loaded it up with modules.

For core/core modules you have the only problem with News (bring your templates in DB: read help of new News module), but for Feedback Form I don't think that works on 1.2X (please consider FormBuilder module for this) and other modules? Depends ....

For your installation (old and unsupported modules) you MUST consider a test locally before making the jump in production.
In this way you can upgrade core and modules and substitute unsupported modules and if WORKS you can MOVE site from local to production (doc or Sitepusher module) after BACKUP of site production

Look this for an example

Alby

[calguy1000]

Yes, as Alby said, if your site is 100% critical, I would suggest you copy the site to a test location, and test the upgrade process there first.

FeedbackForm is discontinued and no longer maintained, and does not work on CMS 1.2.x  so you will have to move to FormBuilder

[doug_n]

alby and calguy1000, what can I say except a MILLION times thank you!!

Your responses are absolutely what I needed to hear.

This site is 100% critical.

In fact, I had just started a discussion with with my colleague, and with the client in this project, about the many issues involved in this whole upgrade process, and a test location was one of the first ideas we started kicking around.

So hearing this kind of confirmation is fantastic.

I will research the link provided, and whatever else I can find, on setting up a test location.  If I have more questions, I'm sure I can count on this great forum for support. 

I'm really enthusiastic about CMSMS, and I'd like to spread it's use around as much as possible, relating to sites I deal with in my advertising and design business.  Knowing this forum is so supportive is a huge plus.

Thanks again,
~Doug