Answer the question
In order to leave comments, you need to log in
Answer the question
In order to leave comments, you need to log in
You do not need to install all versions in turn - Moodle has a fairly powerful system for upgrading and converting the database.
However, some versions still cannot be skipped: this is how developers reduce the amount of code that needs to be maintained (after all, the system has existed since 2002).
When upgrading from 3.0 to 3.5, you must first upgrade to 3.1
Please note that these versions have different system requirements.
For this reason, you cannot use auto-update. In general, it is better to never use them, so that it is not excruciatingly painful.
I would do this:
- Turn on maintenance mode
- Make a full backup, including code, database and Moodledata.
- Replaced the code with version code 3.1.x, except for config.php
- Updated to 3.1
- Checked the safety of the content, settings and learning history (everything should be fine, the versions do not differ much, but, as they say, it's better to be careful).
- Prepared a new server for version 3.5 (take your time with 3.6, it is short-lived, live on 3.5 until 2020, then go straight to 3.9).
- Made an archive of the database and Moodledata
- Deployed the archive on a new server.
- Deployed the code of the latest version from the 3.5 branch there
- Transferred config.php, correcting the database connection parameters and the path to Moodledata in it
- I went into Moodle and started the upgrade procedure.
- Checked the safety of materials and ratings
- Made a full copy
- Turned off the maintenance mode
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question