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

Upgrading to Moodle 2.0: Difference between revisions

From MoodleDocs
m (roadmap link)
m (del specific, my bad)
Line 1: Line 1:
{{Moodle_2.0}}
{{Moodle_2.0}}
{{stub}}
{{stub}}
Moodle 2.0 is in beta status and is relatively stable but still not suitable for a production server.  It includes some major changes.  See [[Roadmap]] for links to the changes.   
Moodle 2.0 is in beta status and is relatively stable but still not suitable for a production server.  It includes some major changes.  See [[Roadmap]] for outline of changes and links.   


For example:
*Themes have been restructured. The list of standard themes will be different than in previous versions.


==Table of Contents==
==Table of Contents==

Revision as of 12:44, 11 April 2010

Template:Moodle 2.0

Moodle 2.0 is in beta status and is relatively stable but still not suitable for a production server. It includes some major changes. See Roadmap for outline of changes and links.


Table of Contents

Before upgrading please...

  • Always check your site to make sure it 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
  • 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.

See also