Opigno Update to 2.2

spensort
Forums
Support
Hi, I am trying to update my Opigno 2.1 (Drupal v. 8.6.7.) site to the latest 2.2 version (drupal 8.6.10) using composer. I ran the following command composer outdated opigno/opigno_lms as recommended by the user guide. Although I got a list of results, instead of being for Opigno 2 on drupal 8, they looked to me more like Opigno 1 results. Are these results correct or is there something wrong with my installation? Kr, Chris name : opigno/opigno_lms descrip. : Opigno LMS profile keywords : versions : * 1.2.0 latest : 1.3.0 type : drupal-profile license : GNU General Public License v2.0 or later (GPL-2.0-or-later) (OSI approved) https://spdx.org/licenses/GPL-2.0-or-later.html#licenseText source : [git] https://bitbucket.org/opigno/opigno_lms.git c60eac9bb96a55bcffd6c1aaf0fe7348649218b3 dist : [zip] https://bitbucket.org/opigno/opigno_lms/get/c60eac9bb96a55bcffd6c1aaf0f… c60eac9bb96a55bcffd6c1aaf0fe7348649218b3 names : opigno/opigno_lms requires drupal/opigno_calendar 1.1.0 drupal/opigno_calendar_event 1.1.0 drupal/opigno_catalog 1.1.0 drupal/opigno_certificate 1.1.0 drupal/opigno_class 1.1.0 drupal/opigno_commerce 1.1.0 drupal/opigno_course 1.1.0 drupal/opigno_dashboard 1.1.0 drupal/opigno_forum 1.1.0 drupal/opigno_group_manager 1.1.0 drupal/opigno_ilt 1.1.0 drupal/opigno_learning_path 1.2.0 drupal/opigno_messaging 1.1.0 drupal/opigno_migration 1.1.0 drupal/opigno_module 1.1.0 drupal/opigno_moxtra 1.1.0 drupal/opigno_notification 1.1.0 drupal/opigno_scorm 1.1.0 drupal/opigno_search 1.1.0 drupal/opigno_statistics 1.1.0 drupal/opigno_tincan_api 1.1.0 drupal/opigno_tour 1.1.0 drupal/platon 1.1.0 drupal/tft 1.1.0
axel
Thu, 02/28/2019 - 16:36

Hi spensort,

Hi spensort,

It's correct, the version on drupal.org of Opigno 2.2 is 8.x-1.3

2.2 is the marketing name, easier to remember

8.x-1.3 is the technical name

I hope that helps

spensort

In reply to by axel

Thu, 02/28/2019 - 18:29

Security UPgrades 8.x-1.3 disguised as 2.2 !

Hi Axel, Yes, it does, thanks :) Only trouble was when I tried to upgrade the site using the command composer update opigno/opigno_lms --with-dependencies, it said:- - Dependency "drupal/entity" is also a root requirement, but is not explicitly whitelisted. Ignoring. - nothing to install or update!? Is there something I should be doing with the settings.php file, such as taking a back-up of it and editing some setting before running the composer update command presented in your user manual? Kr, Chris
axel
Thu, 02/28/2019 - 19:11

Hi Spensort,

Hi Spensort,

No you don't need to do anything special with settings.php

But a global backup (files and database) is of course highly advised

spensort
Fri, 03/01/2019 - 08:38

JSON file replacement

Hi, So the json file replacement and update instructions in your user guide for 8.x-1.3 version are for the Opigno 2.2 ? If I understood correctly I need to: 1. make a secure backup copy of the current json file. 2. Replace it with the one downloaded from your user guide to lifts the restrictions for updating the environment. 3. Manually copy any contrib-module requirements and other unique specifications into the new json file. 4. Run Composer update 5. Run update.php Do I then just leave the json file as is, or do I revert to the original one that may have some unique shared hosting environment specifications? The Hosting tech team support created the composer set up for me, so I am a little nervous of messing about with it. Kr, Chris
axel
Fri, 03/01/2019 - 09:13

Hi Chris,

Hi Chris,

At step 1 you should do a full backup, not only composer.json, it's safer

Then your steps are correct.

You can leave afterwards the new composer.json file, no risk at all.

Best regards,

spensort
Fri, 03/01/2019 - 10:11

Advice Validation

Great, thanks Axel. As a point of further interest, I have also received the following advice from elsewhere... " Would change the version constraint on drupal/core to ~8.6.10 minimally. That would allow you to keep current for Drupal. You would need to check the patches for core and remove those contained in the maintenance release when updating. " Do you agree with this? If so, what does 'checking the patches for core and removing those contained in maintenance release' actually involve? Kr, Chris
nikolay

In reply to by spensort

Mon, 03/04/2019 - 09:59

Hi, Chris

Unfortunately, in some technical reasons, we can't implement minimal core version for Drupal on Opigno now (we use a few dev modules and have some problems with installing and updating for these modules). When these modules will be stable the Opigno updating will be easier and more comfortable (we hope that this will be possible in near future). Best regards