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
I need to upgrade PostgreSQL that comes with Chef Server.
/opt/opscode/embedded/postgresql/9.2
It's been installed from binaries, not apt, and the installation directory path suggests that it's an embedded version. Although I'm able to access it remotely just fine.
Has anyone tried patching the built-in PostgreSQL that comes with Chef?
My target version is 9.5 as I need support of json functions available in 9.5.
I'd like to create a local copy on my Windows 8 machine to further develop existing extensions and test upcoming updates of a Typo3 6.1.7 installation. I tared everything up including the MySQL DB dump, extracted it into a fresh install of XAMPP and imported the database. After adjusting the DB and OpenSSL settings in the LocalConfiguration.php I tried to login with my password, but I get a message stating my credentials must be wrong.
The LoginSecurity on BE is configured with RSA, and the InstallTool states that my OpenSSL config is running correct. Then why can't I login? What did I miss?
Searching what could be wrong I looked at the requirements for Typo3 6.1.x, and it clearly states that it supports MySQL 5.5.x. Sure enough, the freshly installed XAMPP uses MySQL 5.6. I removed it, installed the other current XAMPP package with MySQL 5.5 and now it works.
I am taking the "mongodb for node.js" course and trying to import/restore data to my mongolab instance but I keep getting Auth err code 18 errors.
I can connect to any instance I create using the mongo --shell from the nitrous.io box and it works fine. So my connect string and env variables are correct. If I change the password when logging in to mongo shell it actually gives me the opportunity to put in the correct password. So I know the user authentication is proper.
I am confused as to why I still get Auth err code 18 errors when I try to use the supplied mongodump files.
I have also tried specifying individual .bson files and that gives the same error as well.
I am connecting to mongod version 2.4.6 but mongorestore is only 2.0.4 on the nitrous.io box. I wanted to update to the newer version and see if this is the problem. I have read other posts from other sites where this seemd to break in version 2.2.2. while importing using older versions of the binaries for restore.
it does not appear you(nitrous.io developers) leave a way to update or support mongodb versioning. Do you have a way I could update to mongodb v2.4.6?
also if you could add htop and bmon to your image that would be nice.
Nitrous has released a package manager dubbed autoparts which will allow you to install mongodb 2.4.6.
Autoparts requires you to have a Nitrous box on version "bran" or later. If you are on version "arya" then you will need to download the contents within your box (SCP or Nitrous Mac App), terminate the box, followed by creating a new box in order to upgrade.
Take a look at the README within the Github Repo for instructions on how to use autoparts:
https://github.com/action-io/autoparts
To install/update mongodb to the latest version, run the following command:
parts install mongodb
After the installation completes, run mongo in the console to check the version. You may need to restart the console if it is reporting an older version.
Hey I have mongodb which I have used for a long time. It's version is 1.2.2.
Now I have new server running centos 5.5. I know how to install mongodb on it.
It's version is 1.6.5.
I want to know how I can migrate my db files in /var/lib/mongo/ to 1.6.5?
It's just dbs and collections, no index files at all.
Is there any tools can easily do that for me?
Copy over the original database files to the new server and restart mongod on the new system.
It might be necessary to to start mongod with the --upgrade option in order to migrate existing database files to a new database format (has not changed since 1.4 but possibly between 1.2 and 1.6).
If you want to upgrade to the just released 1.8.0-rc0 detailed instructions are at http://www.mongodb.org/display/DOCS/Upgrading+to+1.8.0