Before any upgrade, a full backup of your Opigno instance (database and files) should be done, so that you can revert to the previous version in case the upgrade doesn't go well.
If you want to quickly check if your Opigno instance is up-to-date, you can simply click in the user menu on "About". You will see your version of Opigno as well as a green pictogram if it's up-to-date:
...
| Info |
|---|
This assumes that you are already using Opigno 2.x (this does not cover upgrading from Opigno 1.x branch). This also assumes that you initially installed Opigno using Composer. If you initially installed Opigno by downloading the tarball version, upgrade with Composer won't work. As of Opigno 3.x, only Composer is advised for installation and upgrade. |
Update to
...
Opigno LMS 2.28
If there are updates for Opigno LMS you can easily install them with Composer.
...
Install updates:
- UPDATING TO 8.x-2.28 version: get this composer.json file. Then replace your old composer.json with a new one and then run the commands below
| Note |
|---|
NOTE: if you already installed some packages that are not part of Opigno LMS you should include them in a new composer.json file, otherwise Composer may remove them |
| Code Block | ||
|---|---|---|
| ||
// Clear composer cache composer clearcache // Check if updates will run without any issues composer update --dry-run // Run updates composer update |
During the update process, some warnings may appear in relation with some modules (drupal/calendar, drupal/views_role_based_global_text), mentioning that they were modified, and asking "Discard changes?". The answer should be "y".
These modules will be updated to new versions.
Then update database and clear cache in admin interface or by Drush:
...