Update
From Lanius CMS Wiki
When a new release of Lanius CMS is out you can update to the latest version with an incremental patch. For example, if you have v0.5.0 and the latest version is version 0.5.1, the update patch applies only to Lanius CMS v0.5.0 and not previous versions.
There are two types of update patches:
- normal update patch, which needs to be installed via the CMS itself
- overwrite update patch, which can be dropped over an existing installation
You can use the latter if your PHP server does not allow write access to files. In such case you will get some errors and will have to manually re-activate the index.php of the website by moving the index_new.php file over the temporary index.php.
In case of failed update (it can happen), you might want to revert to a Manual Update as explained below.
Contents |
Update instructions
This is the correct procedure to update a Lanius CMS website:
- disable your non-English languages (if you are using it) from the Languages Manager;
- put website offline from Global Configuration;
- make a database backup from Database Manager;
- make a full (data + sources) website backup (this step is optional but a full backup might be used as last resort in case of major update failure) using Tarball Backup;
- apply patch
- put website back online
- enable your non-English languages only after having updated them to the new version of Lanius CMS
See also Backup for extended information about backup in Lanius CMS.
If you have subsites, they will need to be updated after the main site update. See Updating a Subsite.
Update patch
An update patch filename looks like update_from_v0.5.0_to_v0.5.1.zip.
This update can only be installed via the 'Install patch' feature available from administration backend. Manually extracting the patch content would result in an unusable CMS.
An update patch can only update Lanius CMS from the before-latest version to latest version
Revision update patches
Revision update patches can occasionally be released to update a main release with hotfixes. Such patches do not require installation and neither database changes, they are mere changes to PHP source files.
You can apply these patches by simply extracting their content into your Lanius CMS installation; the latest release always includes such patches, you only need to use them if you have a released version but the revision has been changed (you can notice this because the green status picture becomes red and urges to update).
Overwrite patch
An overwrite patch filename looks like overwrite_update_from_v0.5.0_to_v0.5.1.zip.
These are instructions to use the overwrite patch:
- the package should be extracted over the previous version in order to work correctly
- open page install/update.php on your website to apply the necessary changes (to database and config.php).
- finished
If you get some file errors at the end of the update process, don't worry: just rename the index_new.php file to index.php and remove install/update.php. (This is only valid IF the database update process was successfully finished)
Veloce_sfx overwrite patch
This type of overwrite patch can be extracted automatically using veloce script.
Manual update
See Backup for instructions about a full website backup, which is necessary if you want to accomplish a manual update.
Only this process works for updating any version to the latest version (not necessarily for an incremental update like previous).
Migration
If you have a database backup created with Drake CMS or Limbo CMS you can easily import it by placing it in the private/backup directory and then restoring it using the System -> Database -> Backups page.
If you can create a tarball backup with Drake CMS or Lanius CMS, then follow instructions in Manual Update
