Updating your LORIS

Updating your LORIS

We recommend upgrading to the most recent LORIS release.

If you are a developer used to working on the development branch, note that the master branch reflects the last stable release. e.g. 17.1-dev is the next development branch after 17.0.*

We do not support the unstable pre-release development branch.

Update your LORIS in a few steps:

• Download the new release codebase. Be careful of overwriting any custom code modifications that you may have added - you'll want to merge these with the code updates.
• Run composer install --no-dev to update dependencies and re-generate the autoload.php file
• Apply the MySQL release-upgrade patch found in the SQL/ directory. Carefully note modifications to data columns and data type definitions
• Check your project/ directory for code that may be overriding the main Loris codebase - these files may need updating to work with the release codebase. Note that as of 16.0 release, custom module support has changed.
• Review all Release Notes for every release since your last version, including minor releases -- especially those in the section specifically for Existing Projects. Follow carefully the recommended steps for existing projects
• Pull requests tagged with Caveat for Existing Projects.
• 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/)
• Finally, re-grant your admin user all available permissions:

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

Imaging projects:

Update your Loris-MRI code, carefully note changes to the imaging pipeline script and tables, and all recommended steps in the Release notes for Existing Projects.
Pull requests marked Caveat for Existing Projects mean that there may be changes to your data after upgrading.

Upgrade Tip: It may help to update tables to utf8 character set:

ALTER TABLE users CONVERT TO CHARACTER SET utf8;