My b2evolution Version: 2.x
Here is my plan for upgrading from 2.2 to 2.3 tonight:
1. Backup the php database using cpanel (and dig up the database password and user id).
2. copy the blogs directory to a safe place
3. unzip the 2.3 files on the server
4. make the custom edits that I need to make (especially in ./conf for multiple domains)
5. delete the current blogs directory
6. move the newly unzipped blogs dir to the just deleted (old) location.
7. run the install script
8. delete the install directory
Should that work? Did I miss anything?
I was thinking maybe a better way to manage this in the future would be to install each new version in it's own directory and then just sym link from blogs to whatever instal that I want.
Will that work on the php side, or does the installer do schema upgrades that would break old versions?
Thanks,
Mark
General Support
b2evolution CMS Support Forums
texasag90 wrote:
When going from 2.2.0 to 2.3.0-RC1 there is no database change, so *technically* you don't need a backup. Obviously having a backup is better than not having one, but for the sake of reverting if you choose to do that you don't have to worry about your database.
OTOH I actively push ALL users of any beta release to upgrade whether they want to or not. Players won't play with an old beta is the reason. Everyone on the developer team is going to use either the latest release OR play with stuff no mortal should play with. "CVS" is scary yah?
Anyway your plan seems strong and safe. Personally I do it differently, but the end result of your plan is (technically) a bit stronger and safer than my method.