best practice to upgrade 0.963 rc1 to evolution 1.02

Hey All,

Sorry for dumb question. I am about to do an upgrade and was wondering if I can upgrade directly from 0.963 to 1.02. I was planning on renaming snippets / plugins I didn’t want overwritten, and I know that managermanager will be a new version. I usually upgrade straight up the upgrade path as new versions are released, but this site has not been upgraded in a while and I forgot if I could skip versions and go straight to evo 1.02.

Any known issues off the top of your heads I should be aware of? Any nightmares? Or do I just follow the normal upgrade instructions inside wiki that I have used on countless other oocasions?

-Noah

I have done this particular upgrade a couple times without incident, so it worked for me, except...

One time I ended up with a problem, as I was asked to upgrade a site, and no one told me that they had made some Ditto changes before.

Fortunately, I had backed up the files first. All files! I would recommend this, as when you’re working on lots of sites, who can remember everything?

I can troubleshoot quickly, so I was able to isolate the problem rather than simply reloading all the old code, which could have been messy.

good luck!
D

Edit: I spoke a little too soon... I did update to 1.02 from 0.963, but not the "RC", or release candidate. The same principles should apply, though.

When updating an older site, I usually avoid updating the assets/ folders. This includes uploading the files as well as having the checkboxes cleared during the upgrade process. Then if I feel it’s necessary I can update the snippets and plugins one at a time to make sure nothing breaks.

Quote from: sottwell at Mar 22, 2010, 05:14 PM

When updating an older site, I usually avoid updating the assets/ folders. This includes uploading the files as well as having the checkboxes cleared during the upgrade process....

Hello

Please could you explain a bit further - when you say "this includes uploading the files" do you mean NOT uploading the assets/* folders so the older asset folders remain while the remainder of the site code is new? If so, I work on the server via SSH so it would appear that I should rename my existing assets folder, unpack the new site code and then rename the original assets folder back again?

Does that make sense?

Thank you for your time

L

Whatever it takes to preserve your existing assets folders.