Symphony.

Step 3. Update Files

Package-based upgrade

The package-based upgrade is just like the package-based installation, except you'll need to avoid overwriting your customizations. Let's begin by downloading the current release, and be sure to have an FTP client handy. When you're ready to go, login to your Symphony website as an administrator.

Now extract the new release's zip package and overwrite your site's symphony folder by uploading the new symphony folder. Do the same for update.php and index.php. Can't find update.php? Congratulations, you must be updating to the 2.3 branch of Symphony, which means you'll need to overwrite index.php and bring in the install folder. Last, you will need to overwrite Symphony's core extensions with the new versions, but don't overwrite the whole extensions folder, since you probably have some custom extensions you want to keep.

You may also overwrite any custom extensions with new versions, which is optional unless the Symphony upgrade breaks compatibility with the extension(s) you're running.

Git-based upgrade

Using Git can make the upgrade process completely painless! In the most basic scenario, you can simply SSH into your site's host, and issue the following commands:

cd /path/to/your/site
git pull

this will update the Symphony core files for you automatically. Follow this up with:

git submodule update

and you should be ready to go.

Handling conflicts

It's common to get stuck with conflicts, due to deviations between your site's files and those in the Symphony repository. If you run into a submodule error during the git pull step, you'll need to stash your changes:

git stash
git pull origin master
git stash apply

Note that you may have to individually resolve conflicts with git add or git rm during the git stash apply step.

Step 4. Run the updater →