Installing newer version

[argos]

Hi,

I happily run version RC2, but I am curious about RC3. I would like to install it, but I am afraid I will mess things up. When I search the forums I see a lot of messages about things going wrong, and what to to and what not to do. I often see the warning "backup first". Well, that's all very nice, and I certainly will backup everything. But now I wonder what to do with the backup if installing RC3 fails. Return to RC2? Or can I import the RC2 data into the new installation? And the most important question: what should I do -step by step- when installing RC3? I see too many posts about too many errors and hacks and patches etc, to be confident in going to RC3. If I would have a step by step manual on what to do to get a good running new version with all current data preserved I would be very happy... It's just too technical now to take the risk. At least, that's how I feel.

[pSouper]

don't be scared A,
I have just updated my setup in five minutes without hitch.
backup you current database using phpmyadmin to a .sql file then...
just zip up you current site > copy all the rc3 files over what you have.
then correct the details for...

• conf.inc.php
• any changes you may have made to conf.defualt_template.inc.php
• add additional styles you have created from old frontend.css to new one
• re apply any mod you used
• execute the unpdate.sql file from within phpmyadmin's sql query window

upload your new RC3 site

messed it up?

• If all goes wrong with your sites functionality just unzip your RC2 site over the top of the RC3 site
• If all goes wrong with your site's content follow step1 then drop you database and reapply the backup.

[argos]

OK, I'll try tonight, when clients are asleep and can't see a f*cked up site

Thanks for replying!

[argos]

Well well, it took my some hours and a lot of tweaking, but it's up and running again, with RC3.

[GreenNuggs]

Thanks pSouper. This thread was SOOOO key to helping me get through the upgrade. It really should be a sticky.

Another thing to add would be to backup/update the frontend.css file as well.

[argos]

Another thing to add would be to backup/update the frontend.css file as well.

YES, good suggestion! I did forget to backup that file myself. It took a lot of extra time to get the CSS-settings back... Well, I have learned from this upgrade and now I know better what to do next time.

[cfphpwcms]

Since you learned from your experience would you mind posting what you did learn. I'd like to go to RC4 but have the same worries that you had. In fact it seems there should/could be an upgrade procedure listed. I'd be happy to help compile this. Especially if there is a major upgrade coming I'd love to have this down.

Thanks

[pSouper]

You can use the exact same advice from RC.x to RC.x without a hitch.

[argos]

Since you learned from your experience would you mind posting what you did learn. I'd like to go to RC4 but have the same worries that you had. In fact it seems there should/could be an upgrade procedure listed. I'd be happy to help compile this. Especially if there is a major upgrade coming I'd love to have this down.

Thanks

Well, I learned to have a local copy of all files and databases, and I came to the conclusion that I had made more changes in more files than I remembered in first instance. I had to spend more time retweaking than I had expected. So the next time I will make sure I really have everything available as local sources, not just a single Plesk backup and the original installation. But all in all it is very "doable". Just don't think it is done in half an hour