Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Upgrading to Moodle 1.6.

Upgrading to Moodle 1.6

From MoodleDocs

Note: This page needs some more work. Moodle1.6


Since the changes for the upgrade from Moodle 1.5.x to Moodle 1.6 not only change the database structure, but also the database content, some considerations are important before you start.

Check the system requirements

Go to Administration >> Environment and choose Moodle 1.6 ;-) You will get a report of whether your server specs meet the requirements for Moodle 1.6 and what needs to be done.

Update the Moodle files

Perform a normal upgrade of your Moodle installation, taking special care when backing up the database. Take care to include ALL optional modules you have in your existing installation. Conversion of the data to UTF-8 of these modules will not be possible if you forget this.

Database migration

Although not strictly necessary, it is highly recomended that you migrate your database to UTF-8 immediately after upgrading. Check if your site works properly (e.g. no missing optional modules) first.

If you run your site in one language only, select this option to save a lot of time on the migration. Otherwise, Moodle will figure out how to do the migration for every piece of data based on the language of the user, course and your Moodle site. Since the migration is a process which causes heavy processor and disk load and can take a long time to perform, you should choose the moment of the upgrade carefully. It might be good practice to do that on a test installation first if you have one.

The migration process places the Moodle installation in maintenance mode, so non-admins cannot login. In order to avoid having to restart the migration process, it is recommended that the value of max_execution_time in the php.ini file be set to 0 so that the process does not timeout. After the migration is completed, the execution time can be set back to your preferred setting. The migration process saves its current state frequently during its execution, so should it need to be restarted, it will begin near to where it finished. However, once started it needs to finish before the installation can be used by others.

Languages

An entirely new interface for languages has been designed. After the migration of the database, you may go to Administration >> Configuration >> Language and follow the 'Language import utility' link. You may select the desired language packs on the right pane and install them directly. Updating the language packs can now easily be done by following the update link. So you can let Moodle 1.6 download and install the language packs for you.

Custom made new language packs go in moodledata/lang. They have to be in a xx_utf8 folder and should be utf8 encoded.

Localisations of an existing xx_utf8 language pack should be called xx_utf8_local, should be utf8 encoded and should also be put in the moodledata/lang folder. It is still possible to give it another name like xx_mypack_utf8, but then you should add the parentlanguage string in moodle.php from your localisation.

Take care to use always a language pack that matches your database content:

* Upgraded installations: first database migration, then utf8 langpacks
* New 1.6 installations: immediately use utf8 langpacks

You will not find the en_utf8 language pack in your moodledata/lang folder. It is in the moodle/lang folder and is not to be modified at all. It should never be upgraded, since it is part of the installation. All other language packs, even modifications for the en language pack go in the moodledata/lang folder (and are in the case of the en language pack called en_utf8_local or en_xx_utf8 but then with parentlanguage string in moodle.php)

See also