...
Warning | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
It is not always possible to upgrade multiple versions in one step. When this is not the case, if you attempt to skip a critical release you will see this message when trying to update the database schema:
You must download and upgrade successfully to the specified version. This is the list of versions that block upgrading:
|
Info | ||
---|---|---|
| ||
You should review the general installation instructions to check for any changes to minimum version (eg: minimum PHP version) and other requirements. |
Backup Your Database
While upgrading is usually a fairly straightforward process, from time to time fairly significant database changes are made. Efforts are made to make these changes transparent, but as a precaution you should create a backup of your database prior to upgrading in case you need to revert the upgrade.
...
- When upgrading to or past v1v2.10.0, before continuing you may need to create symlinks to Plugins you were previously using. For more details, see Upgrading Registry to v2.0.0.
...
Once you upgrade to this version | You should drop these tables (if present) |
---|---|
Registry 0.8.2 |
|
Registry 2.0.0 | cm_organizations |
Registry 3.3.0 |
|
Registry 4 1.1.0 | cm_password_reset_organizationstokens |
Version Specific Database Updates
...