Updating your LORIS

We recommend upgrading to the most recent LORIS release.

See additional notes at bottom for Imaging projects

If you are a developer used to working on the development branch, note that the master branch reflects the last stable release. We do not support the unstable pre-release development branch.

Update your LORIS in a few steps:

Important If you are upgrading from multiple versions, e.g 20.0 to 21.0, you must first upgrade to each minor release (e.g. 20.1, 20.2, 20.3) in between, before upgrading to the next major release.

Consult the Release notes for the Upgrade process specific to each release. Back up your database and code customizations before beginning. Typically, upgrading involves:

• Update your dependencies
• Apply the Release Patch to the database
• Run any upgrade scripts provided
• Update or merge custom code to work with the new release, if necessary
• Update data to match type/column modifications, if necessary

Upgrade tips

• Ensure your admin user has all available permissions:

INSERT IGNORE INTO `user_perm_rel` (userID, permID) SELECT DISTINCT 1, permID FROM permissions;

• If old template code continues to be sourced, clear your smarty/templates_c directory where templates are cached (NB: clear smarty/templates_c/ but do not clear smarty/templates/)
• Good to note: Pull requests tagged with Caveat for Existing Projects mean that there may be changes to your data after upgrading.
• It may help to update tables to utf8 character set:

    ALTER TABLE users CONVERT TO CHARACTER SET utf8;

Imaging projects

Update your Loris-MRI code to the latest Loris-MRI release and carefully review the Loris-MRI release notes for changes to the imaging pipeline scripts, config files and tables, and follow all recommended steps for Existing Projects.