upgrading from 2.8 to 3.6

upgrading from 2.8 to 3.6

by Deleted user -
Number of replies: 4

Hello am trying to upgrade from 2.8 to 3.6+


however its always giving me the following error:


version 3.1 is required and you are running 2.8.1+ (Build: 20141205)


however i downloaded the latest version which is 3.6.2  how come its saying i have 2.8.1 !


can someone assist me please in this! its frustrating!

link to check http://bhsmoodle.vibrantlabhosting.com


many thanks

Average of ratings: -
In reply to Deleted user

Re: upgrading from 2.8 to 3.6

by Tim Hunt -
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

You cannot upgrade tform 2.8 to 3.6 in a single step. That is what the error message is telling you.

First you must download and upgradet to Moodle 3.1.x. Then you can upgrade to Moodel 3.6.x.

In reply to Tim Hunt

Re: upgrading from 2.8 to 3.6

by Deleted user -
I tried Tim  to work with 3.1.1  however i got the following error
Fatal error: Cannot use 'object' as class name as it is reserved in /var/www/bhsmoodle/moodle/lib/setuplib.php on line 66

i researched and found out that i need at least 3.4  which i did and got the initial error i posted.


In reply to Deleted user

Re: upgrading from 2.8 to 3.6

by Tomasz Muras -
Picture of Core developers Picture of Plugin developers Picture of Plugins guardians Picture of Translators

Just like Tim has said - you have to use 3.1 first to upgrade as intermediate step. Use the latest version - 3.1.16.

Make sure that your server is suitable for 3.1, the requirements are here: https://docs.moodle.org/dev/Moodle_3.1_release_notes#Server_requirements

Average of ratings: Useful (1)
In reply to Tomasz Muras

Re: upgrading from 2.8 to 3.6

by Colin Fraser -
Picture of Documentation writers Picture of Testers

Hi Marwan, to make this a little clearer, each version of Moodle will change something, that is obvious. For some versions one change may require the additional enabling of a PHP module not previously used or on older table in the database has been changed to reflect a change in the way that table is used or to improve access times or something. Moodle evolves in steps, but cannot support too much backward compatibility. This means the upgrade process has to be done in an order, using changes from previous versions, to work properly. This is why it is better to upgrade in short steps rather than in big leaps. 

To avoid this issue when upgrading Moodle, it is better to use an upgrade policy, not just upgrade when you think of it. Basically, determine when would be the best time to upgrade your Moodle and how often you want to spend the time to upgrade. 

In my case, I upgrade both my active Moodles at the end of year break, so once per year. I do not use the latest version, I use the previous version because the majority of coding issues or security issues have already been detected and dealt with in pre-release testing, the most obvious, but also those niggling, minor issues that appear from time to time are already updated. This implies the release is really stable and I rarely have any issue to resolve so the Moodle runs with minimal intervention.  

The last but one release is the more stable, I believe, but also, the more selfish motive is that I have time to test the latest release. I look at, and try to understand, any new features. I test most common features to keep up with any change in process or procedures to activate and use those features. So far, my "clients", (I volunteer to do this), are very happy with the way in which they get to use Moodle and the support they get, and appreciate it. (I get a bottle of wine or two each year, usually with a glass, but I don't drink and I don't have the heart to tell them so. Saves me money as I pass the wines on to family or friends for birthdays or Xmas, and the glasses usually match so a set of wine glasses every few years is a bonus for someone..smile )