Upgrading / From version 2.2 to current
Note: You are currently reading the documentation for Bolt 3.2. Looking for the documentation for Bolt 3.6 instead?
This page provides an indepth guide of how to move an existing 2.2.x site up to the latest 3.2 release. Since this is a major release you cannot assume that there will be no breaking changes and the complexity of the upgrade will vary a lot depending on how much custom code you have in your current site.
You will definitely make the process smoother by taking the following precautions.
- Make sure you are on the latest stable release of the 2.2.x series
- Make sure that you do a full backup of the site database, uploaded files, config files and the extensions directory.
- If possible have your current install under git source control and test any changes on a new branch which can then easily be reverted.
- If you come across any undocumented issues, let us know by raising an issue on GitHub
- Check that the extensions you need have versions available for Bolt 3.2 on the Market Place
There are basically two methods to update an existing installation. Pick the one that most closely resembles your current installation:
- Basic: This describes the process of setting up a fresh Bolt 3.2 install, and moving over all of your existing configuration, data, themes and uploaded media. Use it if you're using a common Bolt installation.
- Advanced: This describes the process of converting an existing Bolt 2.2 install to Bolt 3.2. Use this method if you're running a non-default Bolt installation, like a customized Composer install.
We recommend the first option, because it allows you to get a fresh install up and running, without hassle or leaving behind too many old files.