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.
...
| 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:
| Code Block | ||
|---|---|---|
| ||
drush updatedb drush cr |
Typical problems:
If updates are available but can't be installed you can run this command to check the reasons why it can't be done:
Code Block language bash composer prohibits opigno/opigno_lms
Upgrade from Opigno LMS 2.x to Opigno LMS 3.x
Updating is possible only from the latest version (at the time of writing this manual it is 8.x-2.28)
...
If your version contains many differences from the standard version, which is often the case on projects, use the instructions step by step, which may be preferable. There will also be a list of all changes to the composer file at the end.
1. Install Drush 10.
| Code Block | ||
|---|---|---|
| ||
composer require --dev drush/drush:^10 |
2. Update a project requirement.
The Opigno LMS 2.x dependency list has been updated to look like this:
...
and Opigno LMS 3.x will install all the necessary packages for you
3. Repository list
We'll come back to the detailed review of the changes and the repository list, but now we will make a few important changes.
...
The minimum required is ready and now you can run$ composer update. As mentioned earlier you can
Troubleshooting
If this fails with Your requirements could not be resolved…you may need to remove composer.lock and vendor folder. This trick will work if all your modules are installed via composer $ composer install
Configuration and content structure changes.
...
Duration field
The duration files type was changed to the entity reference type. This change allows improving filtering on the category page.
...
| Note |
|---|
Because the type field was changed it requires to check the all duration of your courses manually and creating a new taxonomy term for the learning path. |
...
Color theme
The default color scheme was changed so you need to check the custom colors settings after update to the Aristotle theme (in case your site uses the custom theme setting instend of default):
...