I want to upgrade a moodle website currently on version 2.5 to the latest version.
I need to clarify that is it possible to upgrade Moodle 2.5 directly to Moodle 3.3.
OR
As mentioned in the moodle upgradation document
"Note: You can only upgrade to Moodle 3.0 from Moodle 2.2 or later. If upgrading from earlier versions, you must upgrade to 2.2 as a first step."
I can only upgrade to Moodle 3.0.
Please confirm.
Thanks in advance.
In order to upgrade Moodle 2.5 to 3.3, start by backing up your site. This includes:
The Moodle files.
The Moodledata files.
The Moodle database.
Make sure you have everything and that no errors occurred while you were backing it up. If you want to be extra sure, restore it to a different location, maybe even locally on your computer and get it working there. Don't forget to adjust the settings in the config.php file as well as running the Moodle Search and Replace tool (it is not in the Moodle menus). Once you are sure that everything is working, and you still have the original unmodified backup files, you are ready to move on to the next step.
Verify your web server environment
Make sure your web server meets the hardware requirements for Moodle 3.3. Note the changes, especially in memory requirements from 2.5 to 3.3. Also make sure your server meets the software requirements for Moodle 2.7. In fact, when upgrading, it is best to verify the software requirements for every version of Moodle you will be skipping in order to find out which system components you will need to be add before proceeding.
Also, before you get started, make sure any 3rd party plugin and themes added to your site will be compatible with Moodle 2.7 and Moodle 3.3. If not, you will need to upgrade these first. If they are not available for the newer releases of Moodle, check with the maintainer of the plugin/theme to see if there might be an updated version forthcoming. If not, you will either need to fix any problems in the code yourself that may come up, switch to another similar plugin that provides similar functionality or remove the plugin completely.
Re-creating .git
The easiest way to upgrade Moodle is using Git. If Moodle was not installed using the "git clone" command, your installation will likely be missing the .git directory. You can check this by using the "git status" command. If you already have a .git folder, you can skip this section and go straight to Upgrade to Moodle 2.7. Otherwise, here is how you can re-create it:
Take note of the build date for your current Moodle installation. You'll find this on its Notification page near the bottom of the page.
Re-create your .git folder using the following commands:
# git clone a new copy of Moodle into another location
git clone git://git.moodle.org/moodle.git
# Checkout Moodle 2.5 (the version of your current site).
cd moodle
git checkout MOODLE_25_STABLE
Look through the log for a weekly release that is dated the same as your build number. The build number is a date in the following format: YYYYMMDD. Take note of the related commit number.
Next, rollback the files to the commit number of the build. Replace "56e05fced" with the actual commit number.
git reset 56e05fced
Once this is done, copy the just the .git folder into the web root of your current Moodle site.
Upgrading to Moodle 2.7
Before you get started, make sure any 3rd party plugin and themes added to your site will be compatible with Moodle 2.7. If not, you will need to upgrade these first.
git checkout MOODLE_27_STABLE
Login to your website as an administrator. You should see prompts that will guide you through the process of upgrading Moodle.
IMPORTANT: Up to this point, you could just roll back the files and everything should be back to the way it was. Once you move beyond this point, the only way to revert your website will be to delete the whole site and restore the backups you made earlier of your site's files and database.
Follow the prompts to upgrade the database. Be prepared as you may need to upgrade some of the plugins as well or make some upgrades to your web server and/or database environment.
Once you have everything running again, it will be time to upgrade to Moodle 3.3.
Upgrading to Moodle 3.3
Have you upgraded to Moodle 2.7 yet? If not, go back and complete that step first. Don't forget to make sure your web server meets the hardware requirements for Moodle 3.3.
Make sure your server meets the software requirements for Moodle 3.3 in order to successfully complete the upgrade from Moodle 2.7.
Next, upgrade Moodle from 2.7 to 3.3:
# Enable version tracking so that it is easier to upgrade Moodle in the future.
git branch --track MOODLE_33_STABLE origin/MOODLE_33_STABLE
# Upgrade Moodle to version 3.3.
git checkout MOODLE_33_STABLE
As you did before for Moodle 2.7, Login to your website as an administrator. You should see prompts that your database is about to be upgraded. If not, go to the Notifications page under Site Administration. Follow the prompts again to upgrade the database. As before, be prepared as you may need to upgrade more plugins and themes, and will likely need to make some upgrades to your web server and/or database environment.
That's it. If you followed the above instructions, your Moodle 2.5 site should now be upgraded to Moodle 3.3. To get the most out of your upgraded site, be sure to at least read the New Features page for each version of Moodle from 2.6 to 3.3.
To upgrade your site to newer bug/security release of Moodle 3.3, you will need to repeat some of the instructions. Essentially it will involve:
Backing up your site files (moodle and moodledata) and database.
Using the "git pull" command from within your Moodle folder.
Logging in as an administrator and following the upgrade prompts from the Site Administration > Notification page.
Verifying that everything on your site still work as expected.
Bug and security fixes come out every week but are only officially release every 2 months.
Hope you find this information useful.
Best regards,
Michael Milette
Per the upgrade documentation for 3.3 it says "You can only upgrade to Moodle 3.3 from Moodle 2.7 or later." https://docs.moodle.org/33/en/Upgrading
So you must first do an upgrade to v2.7 before you can do an upgrade to v3.3
Also note in the v2.7 upgrade documentation it says "You can only upgrade to Moodle 2.7 from Moodle 2.2 or later." https://docs.moodle.org/27/en/Upgrading
Personally I have found less problems when I do upgrades in smaller jumps. So in your case 2.5 to 2.7.20 is a requirement. In theory you could then go from 2.7.20 all the way to 3.3 but you may want to consider 2.7.20 > 3.0.10 then 3.0.10 > 3.3
I can say that I have actually upgraded Moodle 2.3, and Moodle 2.5 successfully to 3.x, though not 3.3 specifically.
That being said, you have to also take the following considerations:
Are you up to the minimal PHP version? (5.6.something)
Do you have the new modules required by 3.x version (3.3 added a few I think)
Are your modules ready for 3.x?
If you aren't sure of any of these, I would go grab a Vagrant/VirtualBox/Docker setup of Moodle, stage your current site (i.e. install it with the same software you have installed on your production server), and upgrade it locally to ensure everything goes as planned.
First you backed up before any moodle 2.5 upgrade.
Then download new moodle 3.3
After then unzip folder
go to xampp->htdocs->your project
paste and override new folder
Copy your old config.php file back to the new Moodle directory
Sometimes, the environment may cause issues, sometimes the Moodle versions. I have faced both. But managed to upgrade. Last time for upgrade to 3.9.2 installed the old version to local server for reference and did a clean install on the cloud. I have upgraded Moodle 2.x to 3.2 for a couple of institutions. Please feel free to contact if needed.
Few steps to consider in this
Take backup of Moodle app, Moodledata and DataBase
You have to follow the upgrade process twice
First you need to upgrade from moodle 2.5 to moodle 3.0
Now you can upgrade you new moodle 3.0 to moodle 3.3
Why is 3.0.* ok but 3.2 version has to specifically be 3.2.6? Is 3.2.1 ok?
Any version is fine when doing a fresh install with parse-server but from parse.com you will not be able to move to 3.2. Seems that migration tool wont allow it.
I moved to 3.0 and from there did backup/restore to 3.2.
However i would always strongly suggest that one in general runs the latest version if you can.
I do know that all test on mongodb 3.2.6 are passing including geo queries.
I needs to install php5.2 version on my server. Right now php 5.4 is the oldest version installed. Since 2 days. I searched a lot over google but didn't find appropriate guidance yet. Tried a lot of tutorials no works at all. Any suggestion or guidance will be appreciated. thanks
I don't think there is any proper or easy way to revert to php-5.2.x from php-5.4.x; at least not using WHM interface or as an automatic process. Even if you have EasyApache3 you will not be able to downgrade from php-5.4.x to php-5.2.x
Your only option might be CloudLinux which comes with a php selector which allows you to select any php version from php-5.1.x to php-7.x.
You must know that Cloudlinux is not free and the license is around $10/month. They offer a 15 day trial so if you do all the necessary setting within that period you can just use it as much as you want. You won't be able to update it though and some of the functionality might not work as expected after the trial ends.
The PHP versions that you have mentioned are completely outdated and using them would be risky. Cpanel is never going to support it with their newer version. So your best deal would be to update your application/website to latest PHP and host with the latest PHP only
I was going through upgrade process of mysql server. It is mentioned that to upgrade from 4.1 to 5.5 we need to upgrade step by step like first to 5.0,5.1 ...5.4 and then 5.5.
I have some questions :
What if we directly upgrade from 4.1 to 5.5. What might get effected? functionality or problem related to upgrading
Chances to loose data ? Even though I'll take backup using 'mysqldump --all-data-base' option.
Lets say, I have two database. I'll take only two database backup. I'll install latest version of mysql 5.7 and load two database back. What are chances to loose data or get corrupted ?
I'm curious to know this. If anybody tried? Because I need to do upgrade in live server.
Is there any step by step document which tells exact steps to upgrade from 4.1 to 5.5 in linux server
Major new features added to MySQL 5.0 and 5.1 that may not work/won't work in 4.x can be located here:
MySQL 5.0 - http://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html
MySQL 5.1 - http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html
I made some tests with MongoDB 2.1 (unstable debian package). I want to test the code with 2.0 stable to see the speed difference.
Can I simply uninstall mongoDB 2.1 and reinstall 2.0 without caring about the data ?
Thanks
#Stennie replied the question with his comment. I tried and it worked. On the mopngoDB website, the best is to download the legacy-static witch is very usefull for version testing.
Be sure to put the right data path to mongod ;-)