Hello,
What is the best way to upgrade from Moodle 3.1.4+ (Build: 20170119) running on PHP Version 7.0.26-1 to the
latest version?
Thank you!
In reply to Dan Johnson
Re: Upgrading from Moodle 3.1.4+ (Build: 20170119)
by Visvanath Ratnaweera -
The only still supported Moodle release for PHP 7.0 is 3.5 (LTS). For the others, 3.7 and 3.8 you need PHP 7.1 at a minimum: http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases.
Too bad can't rate any higher than a +1 and 'Useful' ... +20 is more like it. ;)
Thanks for sharing!
'SoS', Ken
Hi Ken
Glad that you find the summary http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases useful. I myself refer it often.
It is of course "work in progress" (check the "last edited" time stamp). If you, or anybody else, find an error, please reply here or send me a message.
Glad that you find the summary http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases useful. I myself refer it often.
It is of course "work in progress" (check the "last edited" time stamp). If you, or anybody else, find an error, please reply here or send me a message.
In reply to Visvanath Ratnaweera
Re: Upgrading from Moodle 3.1.4+ (Build: 20170119)
by Howard Miller -
If someone had a few minutes, that table would be really useful in the Moodle Docs wiki
In reply to Howard Miller
Re: Upgrading from Moodle 3.1.4+ (Build: 20170119)
by Visvanath Ratnaweera -
Oh sure, it is not copyrighted!
Only thing, that document writer has to update his version, as I make changes/corrections in my document. In fact a correction came in just this morning. (See the strike through in MySQL column http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases.)
Only thing, that document writer has to update his version, as I make changes/corrections in my document. In fact a correction came in just this morning. (See the strike through in MySQL column http://www.syndrega.ch/blog/#php-and-dbms-compatibility-of-major-moodle-releases.)
Read the release notes.
For 3.8, https://docs.moodle.org/dev/Moodle_3.8_release_notes. That tells you which server software you need for 3.8. It also tells you that you can only upgrade from 3.2. So...
https://docs.moodle.org/dev/Moodle_3.2_release_notes
Think very carefully about the sequence of updating Moodle and server software (especially PHP). Whatever else you do... take backups!!
For 3.8, https://docs.moodle.org/dev/Moodle_3.8_release_notes. That tells you which server software you need for 3.8. It also tells you that you can only upgrade from 3.2. So...
https://docs.moodle.org/dev/Moodle_3.2_release_notes
Think very carefully about the sequence of updating Moodle and server software (especially PHP). Whatever else you do... take backups!!
Another suggestion that might save some legwork ...
Admin Menu -> Server -> Environment.
Update Component.
Use the moodle vesion drop down list to page through 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, and 3.8.
Note both the 'yellows' and the 'reds'.
There's your road map of the 'moodle march'.
If you can clone to another server, same OS/PHP/DB ... same environment ... and it's Linux, make sure 'git' is installed.
Read Git for Admins
https://docs.moodle.org/38/en/Git_for_Administrators
And on the clone server, do a 'side load' of git for highest of 3.1.x ... which is 3.4.9 ... will do a 'dot' version update of 3.1.x code to highest 3.4.9.
If that goes well, it's just a matter of using git commands to set tracking and branch to higher branch ... 3.4.9 -> 3.5.highest - running git pull ...
then php admin/cli/upgrade.php --non-interactive
*BACKUP code + DB
check site
then (if php/mysql/mariadb etc. correct versions for the next step in the march, repeat for 3.6.highest .... wash/rinse/dry/repeat sorta thing.
The catch 22's include themes so probably a good idea to check what theme's come 'stock' with version of Moodle.
And, of course, any addons you might have installed on the system ... check those out @ https://moodle.org/plugins/
You are in for some 'fun' ... afterwards, if you use git and have successfully marched the clone ... then repeat entire process on production, two things will become imprinted on brain ... 1. why did we use git before? 2. why did we wait so long to update/upgrade?
'SoS', Ken