Start Updating moodle

Updating moodle

If so, download the plugin code and copy it to the appropriate location in your Moodle code (see Installing plugins).

New sites are recommended to use this rather than CVS since all Moodle development has moved to Git. On Linux servers, Moodle 2.3 supports running the upgrade from the command line, rather than through a web browser.

This is likely to be more reliable, particularly for large sites.

Note: You can only upgrade to Moodle 2.3 from Moodle 2.2 or later.

If upgrading from earlier versions, you must upgrade to 2.2 as a first step.

If you use cron, take care that is executeable and uses the correct php command: chmod 740 admin/cli/(some configurations need chmod 750 or chmod 755) copy the first line from (if it looks like '#! /usr/local/bin/php5.3', no need to copy ' if necessary.

You can use Git for updating or upgrading your Moodle.

There are three areas that should be backed up before any upgrade: Don't forget to make moodle/(and the rest of the source code) readable by your www server.

Ideally the files should not be writeable by your server.

If your Moodle site has been upgraded through many prior versions it is possible that there will be some problems with the database schema (compared to a fresh 2.3 installation). If your site started life prior to Moodle 2.0 it is a very good idea to check and correct the database schema before upgrading. You should also run the database integrity checks in the XMLDB editor.

Check in the Moodle Plugins directory whether there is a 2.3 version available for any contributed/custom plugins (including themes) that you have previously installed on your site.

The last step is to trigger the upgrade processes within Moodle. Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary.