upgrading from moodle 3.0 (am I making this plan too complicated?)

upgrading from moodle 3.0 (am I making this plan too complicated?)

by Billy Zwiener -
Number of replies: 2

Yes, I realize its way overdue (mostly reasons for neglect was plugins which wouldn't function with current moodle however I reaize I HAVE to update now due to php updates needed) but before yelling at me please advise...

I'm coming up with a hard time strategizing how to upgrade my 3.0 site because the PHP version on the server is 5.6.4. Meaning I can't upgrade too high because then it will break because the PHP version. (at least that's my hunch) So that said, what would be your plan of upgrade with something this out of date? I feel like I'm stuck because if I upgrade my php first , moodle 3.0 will break, and if I upgrade my moodle, it will break because of the old php version. I THINK I need to basically do it in steps but I'm wondering if I'm making this plan overly complicated and would like any advice... 

upgrade to moodle 3.1, 

THEN upgrade to php 5.6.5 on server, 

THEN upgrade to moodle 3.2 

THEN upgrade to php version 7.0 server, 

THEN upgrade to moodle 3.3

THEN upgrade to php version 7.2 server

THEN upgrade to Moodle 3.7

Thanks again for any insight here. Much appreciated.

Average of ratings: -
In reply to Billy Zwiener

Re: upgrading from moodle 3.0 (am I making this plan too complicated?)

by Ken Task -
Picture of Particularly helpful Moodlers

Oh, boy!  The 'double whammy'!   Lovely game ... NOT!

Ok, in all seriousness now ... current version go to Sever Environment ... update the component.   After it updates, your pick list of which Moodle version will grow.  @3.0 - choose 3.1 ... see what the chart says.  Then choose the next version up from that ... see what the chart says - wash/rinse/repeat jotting down changes in your 'moodle march' notes/plan.

Uhhhh ... guess what .. it's really a 'triple whammy'! sad   Database minimums and config of DB as well ... character set, collation, and file type ... Antelope -> Barracuda..  So add that to your 'marching moodle' notes.

So some additions ... newer versions of plugins compat with destination version?

Got room to do a minimum site backup (code,DB dump, and only moodledata/filedir after each step/leap in the 'march'?

All above assumes on a host or with a hosting provider where one can do those upgrades (PHP/MySQL) and make those tweaks at appropriate time.

During the 'march', pay attention to config-dist.php for at one stage there will be a line added for dbcollation = in it - which is hint you probably should have your DB collations match.   Hint: cli scripts in moodlecode/admin/cli/ can help!   But for some of those scripts, must have superuser creds for DB server (if you don't know that, find out before you begin the march).

Also, along the way and at each stop before you do a site backup, go to Notifications and check plugins ... the additionals.  Update them at that stage ... before you backup.

All the above best done with ssh access ... and actually easy if using git to update/upgrade ... on a Linux OS.

References ...

https://docs.moodle.org/dev/Releases

https://docs.moodle.org/37/en/Git_for_Administrators

and something if not on git ...

https://sos.sosoftexas.org/blog/?s=git

https://sos.sosoftexas.org/blog/index.php/2018/09/02/using-git-with-moodle-side-load/

'SoS', Ken

Can I yell at ya know! smile




Average of ratings: -
In reply to Billy Zwiener

Re: upgrading from moodle 3.0 (am I making this plan too complicated?)

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers
You can skip the 3.1 and 3.3 steps...I would upgrade php to 5.6.5 or later, upgrade to 3.2, then upgrade php to 7.2 and then go to 3.7.
The initial php upgrade is just a simple apt-get upgrade. The switch to 7.2 is a little more involved but not bad.
Average of ratings:Useful (1)