Upgrading to Moodle 1.6: Difference between revisions
m (link to es) |
Helen Foster (talk | contribs) m (1.6 template, minor re-wording) |
||
| Line 1: | Line 1: | ||
This page needs some more work. | ''Note: This page needs some more work.'' | ||
{{Moodle 1.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. | 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== | ==Check the system requirements== | ||
Go to | Go to Administration >> [[Environment]] and choose Moodle 1.6 ;-) | ||
You | 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== | ==Update the Moodle files== | ||
Perform a normal upgrade of | Perform a normal upgrade of your Moodle installation, taking special care when backing up the database. | ||
==Database migration== | ==Database migration== | ||
Although not strictly | Although not strictly necessary, it is highly recomended that you migrate your database to UTF-8 immediately after upgrading. | ||
If you run your site in one language only, select this option to save a lot of time on the migration. | If you run your site in one language only, select this option to save a lot of time on the migration. | ||
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 | 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 | The migration process places the Moodle installation in [[Maintenance mode|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== | ==Languages== | ||
An entirely new interface for languages | An entirely new interface for languages has been designed. After the migration of the database, you can go to the language page in the admin menu and follow the 'Language Import Utility' link. You can 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. | ||
[[Category:Administrator]] | |||
[[Category:Installation]] | |||
[[es:Actualización de moodle 1.6]] | [[es:Actualización de moodle 1.6]] | ||
Revision as of 14:28, 10 April 2006
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.
Database migration
Although not strictly necessary, it is highly recomended that you migrate your database to UTF-8 immediately after upgrading. If you run your site in one language only, select this option to save a lot of time on the migration. 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 can go to the language page in the admin menu and follow the 'Language Import Utility' link. You can 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.
