Note: You are currently viewing documentation for Moodle 2.5. Up-to-date documentation for the latest stable version of Moodle may be available here: Upgrading.

Upgrading: Difference between revisions

From MoodleDocs
Main page ► Installation ► Upgrading
Installation
(→‎Possible issues that may affect you in Moodle 2.5: MySQL dmlwriteexception error when using calculated questions in a quiz (MDL-29332))
 
(47 intermediate revisions by 9 users not shown)
Line 1: Line 1:
{{Installing Moodle}}
{{Installing Moodle}}
'''Before you do anything else, read [[Upgrading to Moodle 2.2]]'''
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''


Moodle is designed to upgrade itself from one version to the next. The procedure is
==Check the requirements==
# [[Site backup|Back up everything]].
# Replace the old version of the code with the new one.
# Visit the [[Site_administration_block#Notifications|administrator notifications]] link, which triggers Moodle to self-update.
These steps are explained in more detail below.


Sometimes there are specific considerations when upgrading to a particular version. See the [[dev:Releases|Releases page]] for more information on this.  You also have to be more careful if you have installed additional plug-ins or customised the code.
Check that your server meets all requirements for 2.5 in ''Settings > Site administration > Server > [[Environment]]''.


See this tutorial if you are [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf upgrading Moodle on cpanel]. It is a bit rough around the edges and is a little dated, but you should get the idea.
Note: You can only upgrade to Moodle 2.5 from Moodle 2.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2 upgrade to 2.2] as a first step.


There is also a separate page about [[Ubuntu_Debian_Upgrades|upgrading Moodle if you installed it using the Ubuntu/Kubuntu/Debian package manager]].
==Before you upgrade your site for real==


'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''


__TOC__
== Backup important data ==


When upgrading a Moodle installation you should follow these steps:
There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, your Postgres or MySQL database dump)


==Before you upgrade your site for real==
See [[Site backup]] for more specific information.


You are strongly advised to make a copy of your entire Moodle site onto another computer (see [[Moodle migration]]) and run the upgrade there to verify it will work. If you decide not to do this, make sure you have good backups. If the upgrade fails you will need the backups to go back.
==Put your site into maintenance mode==
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.


==Check the requirements==
== Check for add-on updates ==
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the target version you want to upgrade-to in ''Settings > Site administration > Server > [[Environment]]''.


==Put your Site into Maintenance Mode==
If you have [[Automatic updates deployment]] enabled, you will be able to update installed add-ons automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.
Before you begin upgrading your site, you should put it into [[Maintenance_mode | Maintenance Mode]] to stop any non-admin users from logging in.


== Backup important data ==
If you are updating add-ons manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.5 version available for any add-ons (including themes) that you have previously installed on your site. If so, download the add-on package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing add-ons]]).
See [[Site backup]] for more specific information.


There are three areas that should be backed up before any upgrade:
The upgrade of the add-on will then happen as part of the Moodle upgrade process.
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, the SQL or Postgres database)
 
Experienced site administrators know that it is a best practice (a very good idea) to make a backup of any production system before a major upgrade. In fact, it is a good idea to automate your server to backup your Moodle installation daily.  Most upgrades on sites that have used the standard Moodle packages (no contributed code and no little tweaks to the php files), will not have any major issues with the upgrade process.


:''TIP:'' One more time, "do not risk what you can not afford to lose": do regular backups, make sure it is really backed up and know how to restore a backup!
If an out-of-date add-on causes your upgrade to fail, you can usually delete the add-on code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.


== Install the new Moodle software ==
== Install the new Moodle software ==
Upgrading can be a simple process or a more complicated process.  Sites that have not used contributed code and are migrating from say Moodle 2.x.1 to 2.x.3 '''should''' not have a problem.  However, we still recommend that with any production server that you have made a successful backup of the MySQL database, the moodledata directory and the moodle program folders and files. 
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. Review the backup section above.


=== Standard install package ===
=== Standard install package ===
Having read the cautions about backups, download a copy of the standard install package. Here is a set of simple instructions for an average site.
*It is probably a good idea to use the [[Site administration block]]>Server>Maintenance mode to prevent user activity as the site upgrades.
*Having moved your old Moodle software program files to another location, unzip or unpack the upgrade file so that all new the Moodle software program files are in the location the old files used to be in on the server.  Moodle will adjust SQL and [[Moodledata directory|moodledata]] if it needs to in the upgrade.
*Copy your old [[Configuration file|config.php file]] back to the new Moodle directory. If you've defined individual blocks for new courses you have to delete 'admin' block definition and replace by 'settings' for the new block.
*If you had added any custom plugins or themes into your Moodle you can add them to the new code. It is important to check that you get the correct version for your new version of Moodle. You should check in the optional plugins database. Be particularly careful that you do not overwrite any code in the new version of Moodle. If you are upgrading to Moodle 2.0 or newer, note that all optional plugins and themes required a significant rewrite and most do not have 2.0 versions (yet).
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines or screens indicating progress. 
*After a successful upgrade, turn off the maintenance mode, so your users can get into the site.


=== Using a downloaded archive ===
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
In some installs, the site administrator may overwrite the Moodle code with a backup copy. Or create a new clean install copy of Moodle, then restore an archive (via a compressed file or parts of a saved set of Moodle code files and folders).  
# Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
 
# Copy your old [[Configuration file|config.php file]] back to the new Moodle directory.  
*Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new or "cleaned" installations. The best way is to rename the current Moodle code directory (for example rename "moodle" to "moodleold"), then unpack the new Moodle archive into the old location (for example, a new directory called "moodle").
# As mentioned above, if you had installed any custom add-ons on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.


====Linux====
====Linux====
  mv moodle moodle.backup
  mv moodle moodle.backup
  tar xvzf moodle-1.1.tgz
  tar xvzf moodle-2.5.tgz


Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one ('''check that optional/custom plugins are the correct version for your new Moodle first'''):
Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one ('''check that custom plugins are the correct version for your new Moodle first'''):


  cp moodle.backup/config.php moodle
  cp moodle.backup/config.php moodle
Line 70: Line 53:
  cp -pr moodle.backup/mod/mymod moodle/mod/mymod
  cp -pr moodle.backup/mod/mymod moodle/mod/mymod


Don't forget to  
Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.
 
sudo chown www-data moodle/config.php


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


if necessary.
=== Using Git ===
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.
===Command line upgrade===
On Linux servers, Moodle 2.5 supports running the [[CLI|upgrade from the command line]], rather than through a web browser. This is likely to be more reliable, particularly for large sites.
== Finishing the upgrade ==
The last step is to trigger the upgrade processes within Moodle.
To do this just go to ''Settings > Site administration > Notifications''.
Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!
Note: If you are running multiple servers then you should purge all caches manually (via ''Settings > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.


if necessary.
==After upgrading==
 
The config.php file from your 2.2, 2.3 or 2.4 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.5 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.5 config-dist.php.
==Fatal error: Maximum execution time of 30 seconds exceeded...==
 
If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598 .
 
==Possible issues that may affect you in Moodle 2.5==
 
===Renamed settings block===


where www-data is whatever user the Apache user is on your system. This is often 'apache' or 'www'.
The settings block has been renamed 'Administration' and reports are now located there.
You can find out by doing 'ls -l' in your /var/www/moodle folder (or wherever your moodle site is)
and then looking at the owner and group.


so you may see something like
===Course listing improvements===


ls -l
Course listings are now displayed consistently throughout the site. See [[:dev:Courses lists upgrade to 2.5]] for details of admin setting changes and possible custom theme changes required.
...lots of lines...
-rw-r--r--  1 apache system    784 Jun 28  2007 config.php
...lots more lines...


so the owner is apache and the group is system.
===Google Docs repository plugin upgraded to Google Drive ===


To replicate this on your new system you can do  'chown apache:system config.php'
The Google Docs plugin has been upgraded to Google Drive, supporting folders and new features.


or to do a whole group do
Administrators will need to change their Google API settings to enable access to the Drive API to allow the plugin to work after the upgrade, see [[Google_OAuth_2.0_setup#Registering_with_Google]].


chown apache:system ./*
===Multi-server architectures with different PHP versions ===


and recursively
Moodle has moved to use a more secure mechanism for securing passwords, from 2.5 new passwords will be generated using bcrypt rather than md5. Because bcrypt is only supported for PHP version 5.3.7 and above, it is important that all servers within a cluster use the same version of PHP (MDL-35332).


chown -R apache:system ./*
===Restoring Moodle 2.5 backups to sites with old PHP versions===


=== Using CVS ===
Because bcrypt is not supported in PHP versions below 5.3.7, course backups made using the $CFG->includeuserpasswordsinbackup setting on a site using PHP version 5.3.7+ that are subsequently restored to a site with PHP version < 5.3.7 will require a password reset.


New sites should now use Git rather than CVS (see next section). If your site already uses CVS, to update, just go into the Moodle root directory and update to the new files:
The same issue would occur if you downgraded the PHP version on the server running your site from 5.3.7+ to less than 5.3.7 (MDL-35332).
<pre>
$ cd /path/to/your/moodle/
$ cvs update -dP
</pre>
To update from an older version type in the following:
<pre>
$ cd /path/to/your/moodle/
$ cvs -Q update -dP -r MOODLE_18_STABLE
</pre>


Make sure you use the "d" parameter to create new directories if necessary, and the "P" parameter to prune empty directories.
===Manual grading option in the quiz settings===


=== Using Git ===
Before Moodle 2.5, you could set 'How questions behave' in the [[Quiz settings]] to 'Manually graded'. This caused all questions in the quiz, including multiple choice questions, to require manual grading. This option was not necessary because essay questions, the only ones that need to be graded manually, will always work that way whatever behaviour is selected.


You can use [[Git]] for updating or upgrading your Moodle. New sites are recommended to use this rather than CVS since all Moodle development has moved to Git.
Since the only effect of that setting was that people somehow choose it by mistake, we have hidden it. There should be no circumstances for which you would need to re-enable it, but if necessary, it can be restored by going to ''Administration > Site administration > Plugins > Question behaviour''.


See [[Git for Administrators]] for further details.
===Renamed 'Course availability' setting===


== Finishing the upgrade ==
The [[Course settings|course setting]] 'Course availability' has been renamed 'Visible' and moved into the General section of the form.


The last step is to trigger the upgrade processes within Moodle.  
===New Box.net API===


To do this just visit the [[Site administration block]] admin page (or ''<nowiki>http://example.com/moodle/admin</nowiki>'') and the "Notifications" link.
To continue using the [[Box.net repository]] and [[Box.net portfolio]], the Moodle site must use HTTPS and the plugins must be configured with a Box.net client ID and secret. See [[Box.net APIv1 migration]] for details.


Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.
Box.net repository users will no longer be possible to create a shortcut/alias to a file stored in Box.net.


Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!
'''IMPORTANT''': The Box.net-alias-to-copy-conversion tool should be run ''as soon as possible''. See [[Box.net APIv1 migration]] for details.


===Backup and restore of assignments from Moodle 2.2 and older===


:''TIP:'' Use the site administration block>Server>Maintenance mode to prevent users from changing data during the upgrade.
The [[Assignment module|assignment activity module]] was completely rewritten in Moodle 2.3. Assignments from Moodle 2.2 and older (e.g. from Moodle 1.9) need to be upgraded in order to continue being usable in Moodle 2.5. See the section 'Restoring course backups from Moodle 2.2 and older' in [[Assignment upgrade tool]] for details of what to do.
:''TIP:'' If you are running a large scale Moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing. Post a thread or check the [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum] and check [[Tracker]] for potential issues.


== Verify the upgrade (optional) ==
===MySQL dmlwriteexception error when using calculated questions in a quiz===


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]].
If you're using MySQL or SQL*Server and you have a problem with duplicated keys with the question_attempt_step_data table when using calculated questions in a quiz (from entering a formula which uses variables with the same characters in different cases), it is recommended that you upgrade to Moodle 3.0.x or higher ASAP. Alternatively, the problematic unique index can be dropped or the collation of the columns changed to be case-sensitive, however this is not considered a complete fix. See MDL-29332 for more information.


==Upgrading more than one version==
=== Moodle 2.3 and 2.4 improvements ===


Normally you can upgrade directly from any Moodle version to any later version. So, for example you could upgrade from 2.0 to 2.1, or from 1.9 to 2.2.
If you are upgrading to Moodle 2.5 from 2.2 or 2.3, please see the section 'Possible issues that may affect you' in the documentation [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3] and [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4].


However, every so often, this general rule gets broken, because supporting really large jumps (for example Moodle 1.0 to 2.2 in one step) would be impossible. So far, the break points have been:
==Upgrading from Moodle 2.5 to 2.5.1 or later==
* You must have upgraded to version 1.9.x before you can upgrade to a later 2.x version.
* You must have upgraded to version 2.2.x before you can upgrade to 2.3 or later.


==See also==
[[File:reviewing badge permissions.png|thumb|Reviewing role permissions]]To ensure badge permissions are set correctly for each role archetype, it is recommended that administrators review and change permissions as follows:


*[[Environment]]
# Go to ''Administration > Site administration > Users > Permissions > Define roles'' and click the edit icon opposite a role
*[[Git]] Version control and upgrading
# Click the 'Show advanced' button to reveal the different permission settings
*[[How to fix just one bug without upgrading]]
# Filter by 'badge'
*Moodle.org [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
# Change certain permissions to ensure that all are set to the highlighted value, then click the 'Save changes' button
*[http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial] - screencasts of older Moodle/Cpanel install but useful (also, a very large file that will take some time to load).
# Repeat steps 1 to 4 for each role


Documentation on upgrading to particular versions:
==See also==
*[[Upgrading to Moodle 2.2]]
*[https://docs.moodle.org/21/en/Upgrading_to_Moodle_2.1 Upgrading to Moodle 2.1]
*[https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0 Upgrading to Moodle 2.0]
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.9 Upgrading to Moodle 1.9]
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.8 Upgrading to Moodle 1.8]
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.7 Upgrading to Moodle 1.7]
*[https://docs.moodle.org/19/en/Upgrading_to_Moodle_1.6 Upgrading to Moodle 1.6]


Using Moodle.org forum discussions:
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]  
*[http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs]
* [[dev:Moodle 2.5 release notes|Moodle 2.5 release notes]]
*[http://moodle.org/mod/forum/discuss.php?d=56915 Upgrading from 1.5.2 to 1.7]
* [[dev:Upgrade API|Upgrade API]]
*[http://moodle.org/mod/forum/discuss.php?d=56991 Upgrade nightmares.... any help appreciated]
*[http://moodle.org/mod/forum/discuss.php?d=62463 After upgrading i get "Your site may not be secure." msg]
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]
*[[Beginning_Moodle_2.0_Administration|Beginning Moodle 2.0 Administration]]


[[es:Actualización de moodle]]
[[es:Actualización de moodle]]

Latest revision as of 09:37, 22 September 2016

This page explains in detail how to upgrade Moodle. For a summary of the process, see Upgrade overview.

Check the requirements

Check that your server meets all requirements for 2.5 in Settings > Site administration > Server > Environment.

Note: You can only upgrade to Moodle 2.5 from Moodle 2.2 or later. If upgrading from earlier versions, you must upgrade to 2.2 as a first step.

Before you upgrade your site for real

We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.

Backup important data

There are three areas that should be backed up before any upgrade:

  1. Moodle software (For example, everything in server/htdocs/moodle)
  2. Moodle uploaded files (For example, server/moodledata)
  3. Moodle database (For example, your Postgres or MySQL database dump)

See Site backup for more specific information.

Put your site into maintenance mode

Before you begin upgrading your site, you should put it into maintenance mode to stop any non-admin users from logging in.

Check for add-on updates

If you have Automatic updates deployment enabled, you will be able to update installed add-ons automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.

If you are updating add-ons manually, it is a good moment now to check in the Moodle Plugins directory whether there is a 2.5 version available for any add-ons (including themes) that you have previously installed on your site. If so, download the add-on package. In the next step, you will copy it to the appropriate location in your Moodle code (see Installing add-ons).

The upgrade of the add-on will then happen as part of the Moodle upgrade process.

If an out-of-date add-on causes your upgrade to fail, you can usually delete the add-on code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.

Install the new Moodle software

Standard install package

  1. Move your old Moodle software program files to another location. Do NOT copy new files over the old files.
  2. Unzip or unpack the upgrade file so that all the new Moodle software program files are in the location the old files used to be in on the server. Moodle will adjust SQL and moodledata if it needs to in the upgrade.
  3. Copy your old config.php file back to the new Moodle directory.
  4. As mentioned above, if you had installed any custom add-ons on your site you should add them to the new code tree now. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.

Linux

mv moodle moodle.backup
tar xvzf moodle-2.5.tgz

Next, copy across your config.php, any custom plugins, and your .htaccess file if you created one (check that custom plugins are the correct version for your new Moodle first): 

cp moodle.backup/config.php moodle
cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
cp -pr moodle.backup/mod/mymod moodle/mod/mymod

Don't forget to make moodle/config.php (and the rest of the source code) readable by your www server. Ideally the files should not be writeable by your server.

If you use cron, take care that cron.php is executeable and uses the correct php command: 

chmod 740 admin/cli/cron.php (some configurations need chmod 750 or chmod 755)
copy the first line from cron.php (if it looks like '#!/usr/local/bin/php' or '#!/usr/local/bin/php5.3', no need to copy '<?php')

if necessary.

Using Git

You can use Git for updating or upgrading your Moodle. See Git for Administrators for details.

Command line upgrade

On Linux servers, Moodle 2.5 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.

Finishing the upgrade

The last step is to trigger the upgrade processes within Moodle.

To do this just go to Settings > Site administration > Notifications.

Moodle will automatically detect the new version and perform all the SQL database or file system upgrades that are necessary. If there is anything it can't do itself (very rare) then you will see messages telling you what you need to do.

Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!

Note: If you are running multiple servers then you should purge all caches manually (via Settings > Site administration > Development > Purge all caches) after completing the upgrade on all servers.

After upgrading

The config.php file from your 2.2, 2.3 or 2.4 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.5 there are more/different options available (e.g. database drivers and settings). It's a good idea to map your old config.php settings to a new one based on the 2.5 config-dist.php.

Fatal error: Maximum execution time of 30 seconds exceeded...

If your server uses a main language other than English, you may encounter a 'Fatal error: Maximum execution time of 30 seconds exceeded' when you try to upgrade it. You can increase max_execution_time = 160 on php.ini to allow the scripts enough time to process the language update. Otherwise, you can switch to English as the default language before doing the upgrade and back to your original language after a succcessful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598 .

Possible issues that may affect you in Moodle 2.5

Renamed settings block

The settings block has been renamed 'Administration' and reports are now located there.

Course listing improvements

Course listings are now displayed consistently throughout the site. See dev:Courses lists upgrade to 2.5 for details of admin setting changes and possible custom theme changes required.

Google Docs repository plugin upgraded to Google Drive

The Google Docs plugin has been upgraded to Google Drive, supporting folders and new features.

Administrators will need to change their Google API settings to enable access to the Drive API to allow the plugin to work after the upgrade, see Google_OAuth_2.0_setup#Registering_with_Google.

Multi-server architectures with different PHP versions

Moodle has moved to use a more secure mechanism for securing passwords, from 2.5 new passwords will be generated using bcrypt rather than md5. Because bcrypt is only supported for PHP version 5.3.7 and above, it is important that all servers within a cluster use the same version of PHP (MDL-35332).

Restoring Moodle 2.5 backups to sites with old PHP versions

Because bcrypt is not supported in PHP versions below 5.3.7, course backups made using the $CFG->includeuserpasswordsinbackup setting on a site using PHP version 5.3.7+ that are subsequently restored to a site with PHP version < 5.3.7 will require a password reset.

The same issue would occur if you downgraded the PHP version on the server running your site from 5.3.7+ to less than 5.3.7 (MDL-35332).

Manual grading option in the quiz settings

Before Moodle 2.5, you could set 'How questions behave' in the Quiz settings to 'Manually graded'. This caused all questions in the quiz, including multiple choice questions, to require manual grading. This option was not necessary because essay questions, the only ones that need to be graded manually, will always work that way whatever behaviour is selected.

Since the only effect of that setting was that people somehow choose it by mistake, we have hidden it. There should be no circumstances for which you would need to re-enable it, but if necessary, it can be restored by going to Administration > Site administration > Plugins > Question behaviour.

Renamed 'Course availability' setting

The course setting 'Course availability' has been renamed 'Visible' and moved into the General section of the form.

New Box.net API

To continue using the Box.net repository and Box.net portfolio, the Moodle site must use HTTPS and the plugins must be configured with a Box.net client ID and secret. See Box.net APIv1 migration for details.

Box.net repository users will no longer be possible to create a shortcut/alias to a file stored in Box.net.

IMPORTANT: The Box.net-alias-to-copy-conversion tool should be run as soon as possible. See Box.net APIv1 migration for details.

Backup and restore of assignments from Moodle 2.2 and older

The assignment activity module was completely rewritten in Moodle 2.3. Assignments from Moodle 2.2 and older (e.g. from Moodle 1.9) need to be upgraded in order to continue being usable in Moodle 2.5. See the section 'Restoring course backups from Moodle 2.2 and older' in Assignment upgrade tool for details of what to do.

MySQL dmlwriteexception error when using calculated questions in a quiz

If you're using MySQL or SQL*Server and you have a problem with duplicated keys with the question_attempt_step_data table when using calculated questions in a quiz (from entering a formula which uses variables with the same characters in different cases), it is recommended that you upgrade to Moodle 3.0.x or higher ASAP. Alternatively, the problematic unique index can be dropped or the collation of the columns changed to be case-sensitive, however this is not considered a complete fix. See MDL-29332 for more information.

Moodle 2.3 and 2.4 improvements

If you are upgrading to Moodle 2.5 from 2.2 or 2.3, please see the section 'Possible issues that may affect you' in the documentation Upgrading to Moodle 2.3 and Upgrading to Moodle 2.4.

Upgrading from Moodle 2.5 to 2.5.1 or later

Reviewing role permissions

To ensure badge permissions are set correctly for each role archetype, it is recommended that administrators review and change permissions as follows:

  1. Go to Administration > Site administration > Users > Permissions > Define roles and click the edit icon opposite a role
  2. Click the 'Show advanced' button to reveal the different permission settings
  3. Filter by 'badge'
  4. Change certain permissions to ensure that all are set to the highlighted value, then click the 'Save changes' button
  5. Repeat steps 1 to 4 for each role

See also

Retrieved from "https://docs.moodle.org/25/en/index.php?title=Upgrading&oldid=108161"
Powered by MediaWiki