-
Notifications
You must be signed in to change notification settings - Fork 183
Updating your LORIS
christinerogers edited this page Aug 6, 2019
·
26 revisions
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.
- 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
and thencomposer dump-autoload
to update dependencies and re-generate the autoload.php file - Apply the MySQL release-upgrade patch found in the SQL/Release_patches 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
- 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;
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.