Before upgrading to Totara Learn, please ensure that your server meets the minimum requirements described in the Technical specification.
You will need to be on Moodle versions 3.2.5 to upgrade to Totara Learn 11. See our policy documents, on the impact of forking from Moodle for more information.
- Check the live logs to check if any users are currently using the site. The site will be offline while the upgrades are performed (Site administration > Reports > Live Logs).
- Enable maintenance mode in Moodle (Site administration > Server > Maintenance Mode).
- Back up the Moodle database.
- Back up the moodledata directory.
- Back up the Moodle source code directory.
Replace or merge the Moodle code.
If your Moodle site is not customised you can replace your Moodle code folder with the new Totara code folder and copy your old config.php file to the new folder.
Do not copy the new code on top of the existing code folder.
- If you have customised Moodle you will need to merge your existing Moodle source code and new Totara code. This is best accomplished using a version control tool like GIT or SVN. You will need to:
- Reuse the existing Moodle's config.php file.
- Ensure any themes are updated to work with Totara.
- Include any existing modules and filters remain in the code.
- Resolve any merge conflicts caused by existing local customisations.
- Navigate to admin/index.php using a web browser and perform the install process.
- Click Yes on the Upgrade page.
- Confirm the server status checks.
- Confirm the plugin status checks.
- Proceed with the initial database upgrades.
- Edit the New Admin Settings page if required.
- Continue the database upgrades.
- Check for warnings or errors on the upgrade review page.
- Edit the New Site Settings page if required.
- Test the site functionality. The site should now be displayed with the Totara logos and theme.
- Disable server maintenance mode.
- Congratulations, your site is now running Totara.