Upgrading to Moodle 2.0: Difference between revisions
No edit summary |
(→Before upgrading please...: remind to check for min again (bald guys take note)) |
||
Line 9: | Line 9: | ||
* '''Do a full database backup!''' | * '''Do a full database backup!''' | ||
* Remember to purge PHP cache if using any PHP accelerator | * Remember to purge PHP cache if using any PHP accelerator | ||
* Remember to check minimum requirements, even on a recent complete Moodle install package. | |||
* Read [[Upgrading to Moodle 1.9]] if you are upgrading to 2.0 from 1.8 or 1.7 | * Read [[Upgrading to Moodle 1.9]] if you are upgrading to 2.0 from 1.8 or 1.7 | ||
* Read [[Upgrading to Moodle 1.8]] if you are upgrading from 1.7 | * Read [[Upgrading to Moodle 1.8]] if you are upgrading from 1.7 |
Revision as of 17:37, 20 June 2009
Moodle 2.0
Table of Contents
Before upgrading please...
- Check your site meets all system requirements for 2.0 in Administration > Server > Environment
- Do a full database backup!
- Remember to purge PHP cache if using any PHP accelerator
- Remember to check minimum requirements, even on a recent complete Moodle install package.
- Read Upgrading to Moodle 1.9 if you are upgrading to 2.0 from 1.8 or 1.7
- Read Upgrading to Moodle 1.8 if you are upgrading from 1.7
Upgrading more than one version
In general, it is recommended to upgrade via each version of Moodle, for example 1.8 -> 1.9 -> 2.0. An exception to this is when upgrading from 1.5 or 1.6, when it is recommended that 1.7 be skipped, in other words upgrade 1.5 -> 1.6 -> 1.8 -> 1.9 -> 2.0. (The main reason for this recommendation is that the default roles settings obtained when upgrading to 1.7 are not ideal for 1.8 onwards.)
Now upgrade
Once you have satisfied the requirements for Moodle 2.0, follow the instructions on the upgrading page.
Note, if you get a strange error about 'handling of PHP float numbers', please see this FAQ entry.
Verify the upgrade (optional)
If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at Verify Database Schema.