Difference between revisions of "Upgrading"

Jump to: navigation, search

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

(Check the requirements)
 
(237 intermediate revisions by 52 users not shown)
Line 1: Line 1:
Moodle is designed to upgrade cleanly from one version to the next.  Please refer to [[Upgrading to Moodle 1.6]], [[Upgrading to Moodle 1.7]], [[Upgrading to Moodle 1.8]] or [[Upgrading to Moodle 1.9]]  for particular considerations related to the upgraded version.
+
{{Installing Moodle}}
 +
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''
  
Changes that have been made to the original code, such as installing a contributed module (non-standard module) or a site edit of a php file, may not upgrade. This includes modifications to standard themes, that will be overwritten during an upgrade.
+
==Check the requirements==
__TOC__
 
When upgrading a Moodle installation you should follow these steps:
 
  
==Check the requirements==
+
Check that your server meets all requirements for 3.1 in ''Administration > Site administration > Server > [[Environment]]''. Please note that if you use MySQL you must upgrade the engine to InnoDB since it has become a requirement in Moodle 3.1. See [[Migration from MyISAM to InnoDB]].
Spend some time re-reading the [[Installing Moodle | installation documentation]] and documentation for the new version. Check the system requirements for the version you are upgrading to in ''Administration > Server > [[Environment]]''.
 
  
== Backup important data ==
+
Note 1: The [[Assignment activity]] can now convert various office document formats to PDF to work with PDF annotations. This is optional - but it requires "unoconv" to be installed and configured on the server.  See [https://docs.moodle.org/31/en/mod/assign/feedback/editpdf/testunoconv Unoconv installation].
  
Although it is not strictly necessary, it is always a good idea to make a backup of any production system before a major upgrade, just in case you need to revert back to the older version for some reason. In fact, it's a good idea to automate your server to backup your Moodle installation daily, so that you can skip this step.
+
Note 2: You can only upgrade to Moodle 3.1 from Moodle 2.7 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/27/en/Upgrading_to_Moodle_2.7 upgrade to 2.7] as a first step.
  
There are three areas that need backing up:
+
==Before upgrading==
  
=== 1. The Moodle software directory itself ===
+
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''
  
Make a separate copy of these files before the upgrade, so that you can retrieve your config.php and any modules you have added like themes, languages etc
+
Consider setting the [[Upgrade key|upgrade key]] for your site.
  
=== 2. Your data directory ===
+
== Backup important data ==
  
This is where uploaded content resides (such as course resources and student assignments) so it is very important to have a backup of these files anyway. Sometimes upgrades may move or rename directories within your data directory.
+
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)
  
=== 3. Your database ===
+
See [[Site backup]] for more specific information.
  
Most Moodle upgrades will alter the database tables, adding or changing fields. Each database has different ways to backup. One way of backing up a MySQL database is to 'dump' it to a single SQL file. The following example shows Unix commands to dump the database called "moodle":
+
== Check for plugin updates ==
  
mysqldump -u username -p -C -Q -e -a moodle > moodle-backup-2007-04-01.sql
+
If you have [[Automatic updates deployment]] enabled, you will be able to update installed plugins automatically during the upgrade. Just make sure you check for available updates (via the button for it) at the Plugins check screen.
(The "-a" switch is deprecated and should be replaced by "--create-options")
 
  
Substitute your database user account for username. The -p flag will prompt you for the password for the username specified by -u.
+
If you are updating plugins manually, it is a good moment now to check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 3.1 version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).
  
If your database host is different from the host you want to execute the backup command (usually the web server), you have to specify it with the -h option to mysqldump:
+
The upgrade of the plugin will then happen as part of the Moodle upgrade process.
  
mysqldump -u username -p -h databasehost -C -Q -e -a moodle > moodle-backup-2007-04-01.sql
+
If an out-of-date plugin causes your upgrade to fail, you can usually delete the plugin code rather than uninstalling it from within Moodle so that the data associated with it is not deleted.
  
You can also use the "Export" feature in Moodle's optional "MySQL Admin" web interface to do the same thing on all platforms. This interface can be downloaded from http://download.moodle.org/modules/integrations.php. It is an integration of PHPMyAdmin for the Moodle administration interface.
+
==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. Then you should wait for any currently running cron processes to complete before proceeding.
  
 
== Install the new Moodle software ==
 
== Install the new Moodle software ==
 +
You can fetch the current (3.1) version of the software through
 +
 +
wget http://sourceforge.net/projects/moodle/files/Moodle/stable31/moodle-latest-31.tgz
  
=== Using a downloaded archive ===
+
=== Standard install package ===
  
@Do not overwrite an old installation unless you know what you are doing ... sometimes old files can cause problems in new installations. The best way is to rename the current Moodle directory to something else, then unpack the new Moodle archive into the old location.
+
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
 +
# 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.  
 +
# As mentioned above, if you had installed any plugins on your site you should add them to the new code tree (Moodle directory structure) 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 and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
 +
# Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it.  Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder.  If you are moving your installation to a new server or new location on your server, then you will need to follow the Migration documents.
  
Linux
+
====Linux====
 
  mv moodle moodle.backup
 
  mv moodle moodle.backup
  tar xvzf moodle-1.1.tgz
+
  tar xvzf moodle-3.1.tgz
  
Next, copy across your config.php, any other plugins such as custom themes, and your .htaccess file if you created one:
+
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
 
  cp -pr moodle.backup/theme/mytheme moodle/theme/mytheme
 
  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.
 +
 +
chown -R www-data:www-data moodle (Linux debian - change to appropriate user and group for your OS version)
 +
chmod -R 755 moodle
 +
 +
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.  However, for a simple upgrade, there should be no need to change anything with cron.
 +
 +
=== 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 3.1 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.
 +
 +
If you put your site into Maintenance mode earlier; take it out now!
 +
 +
To do this just go to ''Administration > 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 ''Administration > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.
 +
 +
===Fatal error: Maximum execution time of 30 seconds exceeded...===
  
=== Using CVS ===
+
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.
  
You can use CVS for updating or upgrading your Moodle.
+
==After upgrading==
First you need to do a CVS checkout in your (empty) Moodle root directory.
 
  
You can use any of our [[CVS_for_Administrators#CVS_Servers|CVS Mirror servers]]. Just replace '''SERVER.cvs.moodle.org''' in the instructions below with the name of the mirror server you chose!.
+
The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 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 3.0 config-dist.php.
  
'''For Linux servers'''
+
===Cron===
  
To do a CVS checkout of Moodle, you first have to logon to the Moodle CVS server.
+
Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.
  
  <nowiki>cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login</nowiki>
+
The benefits of these changes are:
  No password for anonymous, so just hit the Enter button.
+
* The schedule for every task can be configured by the admin
 +
* Tasks can run in parallel
 +
* Cron processes use locking to prevent the same task running at the same time by different processes
 +
* Clusters with multiple identical application nodes are supported, you can run cron on all of them
  
Go to the directory where you want the Moodle root to come and type
+
A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner.  To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least ''once per minute''.
  
  <nowiki>cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -r MOODLE_18_STABLE moodle</nowiki>
+
You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure.
  (where MOODLE_18_STABLE is the desired version)
 
  
To update, just go into the Moodle root directory and update to the new files:
+
Before the upgrade to 3.1, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade to 3.1.
  
  cvs update -dP
+
===Assignments===
To update to a new version type in the following and change 18 to whatever newest version upgrade number is
 
  cvs -Q update -dP -r MOODLE_18_STABLE
 
  
Make sure you use the "d" parameter to create new directories if necessary, and the "P" parameter to prune empty directories.
+
The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one.  
  
'''For Windows servers'''
+
If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the [[Assignment upgrade tool]] to un-hide the activities.
  
You can use Tortoise CVS to do the initial checkout and the updates.
+
If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.
  
If you have been editing Moodle files, watch the messages very closely for possible conflicts. All your customised themes and non-standard plugins will be untouched.
+
==Possible issues that may affect you in Moodle 3.1==
  
Don't forget to visit the admin page after the CVS update process has completed.
+
===Assignment submission annotation===
  
== Finishing the upgrade ==
+
The [[Assignment activity]] can now convert various office document formats to PDF to work with PDF annotations. This is optional - but it requires "unoconv" to be installed and configured on the server. See the [[mod/assign/feedback/editpdf/testunoconv|Unoconv installation]].
 +
 
 +
===Competencies===
 +
 
 +
The new 3.1 feature, [[Competencies]], is enabled by default. It may be disabled by an administrator in ''Site administration > Competencies''.
 +
 
 +
===PHP 5.6 bug===
 +
Please note that PHP 5.6 has an upstream bug resulting in some functionality involving AJAX requests to fail on some platforms. It does not affect PHP 5.5 or 7. You need to add '''always_populate_raw_post_data=-1''' to your php.ini. Please refer to [[PHP#HTTP_RAW_POST_DATA_errors|documentation]].
 +
 
 +
===PHP extension xmlreader requirement===
 +
As listed on the Environment page, the PHP extension xmlreader is required (in 3.1 onwards) in order for the downloading of csv, ods, excel etc files in reports and exports to stream progressively.
 +
 
 +
=== MySQL full unicode support===
  
The last step is to trigger the upgrade processes within Moodle.
+
In fresh installs of Moodle 3.1.5, MySQL and MariaDB drivers support full UTF-8. For sites upgrading to 3.1.5, a CLI script may be used to convert to full UTF-8. See [[MySQL full unicode support]] for details.
  
To do this just visit the admin page of your installation e.g. ''<nowiki>http://example.com/moodle/admin</nowiki>''
 
  
It doesn't matter if you are logged in as admin or not. If you are upgrading from some older versions you would not be able to login before the upgrade anyway.
+
See the [[dev:Moodle 3.1 release notes|Moodle 3.1 release notes]] for the full list of changes in Moodle 3.1.
  
Moodle will automatically detect the new version and perform all the database or filesystem 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.
+
=== Moodle 2.8, 2.9 and 3.0 improvements ===
  
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!
+
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation
  
Please note that if you are running a large scale of moodle site (e.g. have more tha 10,000+ courses and 40,000+ users), make sure that you do your own performance profiling testing before you upgrade to Moodle 1.8.x, as there are still quite a few outstanding (unresolved) performance issues in 1.8.x for large user base installations.
+
* [https://docs.moodle.org/28/en/Upgrading Upgrading to Moodle 2.8]
 +
* [https://docs.moodle.org/29/en/Upgrading Upgrading to Moodle 2.9]
 +
* [https://docs.moodle.org/30/en/Upgrading Upgrading to Moodle 3.0]
  
 
==See also==
 
==See also==
  
*Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems] forum
+
* [[Installation]]
*[[Upgrading to Moodle 1.6]]
+
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum]  
*[[Installing Moodle]]
+
* [[dev:Moodle 3.1 release notes|Moodle 3.1 release notes]]
*[[Installation FAQ]]
 
*[http://otaru-jc.ac.jp/hagley/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial]
 
*[http://youtube.com/watch?v=ufAmf_jm_p8 How to backup a whole Moodle site video]
 
*Using Moodle forum discussions: [http://moodle.org/mod/forum/discuss.php?d=26731&parent=125858 Using cvs], [http://moodle.org/mod/forum/discuss.php?d=56915 Upgrading from 1.5.2 to 1.7], [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]
 
 
 
[[Category:Installation]]
 
  
 
[[es:Actualización de moodle]]
 
[[es:Actualización de moodle]]
[[fr:Mise à jour]]
+
[[fr:Notes de mise à jour de Moodle 3.1]]
[[ja:アップグレード]]
+
[[ja:Moodleをアップグレードする]]
[[nl:Upgraden]]
+
[[de:Aktualisierung von Moodle]]
[[zh:升级]]
 
[[pl:Aktualizacja]]
 

Latest revision as of 11:31, 25 April 2019

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 3.1 in Administration > Site administration > Server > Environment. Please note that if you use MySQL you must upgrade the engine to InnoDB since it has become a requirement in Moodle 3.1. See Migration from MyISAM to InnoDB.

Note 1: The Assignment activity can now convert various office document formats to PDF to work with PDF annotations. This is optional - but it requires "unoconv" to be installed and configured on the server. See Unoconv installation.

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

Before upgrading

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

Consider setting the upgrade key for your site.

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.

Check for plugin updates

If you have Automatic updates deployment enabled, you will be able to update installed plugins 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 plugins manually, it is a good moment now to check in the Moodle Plugins directory whether there is a 3.1 version available for any plugins (including themes) that you have previously installed on your site. If so, download the plugin package. In the next step, you will copy it to the appropriate location in your Moodle code (see Installing plugins).

The upgrade of the plugin will then happen as part of the Moodle upgrade process.

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

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. Then you should wait for any currently running cron processes to complete before proceeding.

Install the new Moodle software

You can fetch the current (3.1) version of the software through

wget http://sourceforge.net/projects/moodle/files/Moodle/stable31/moodle-latest-31.tgz

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 plugins on your site you should add them to the new code tree (Moodle directory structure) 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 and that you place the plugin folders in the correct directory (the same directory that they are in in the current installation.)
  5. Your moodledata folder should be located separately to your Moodle code folder and, as such, should not need anything done to it. Moodle 3.0 will throw a warning if it is located in a web accessible folder and the moodledata should never be located in the Moodle code folder. If you are moving your installation to a new server or new location on your server, then you will need to follow the Migration documents.

Linux

mv moodle moodle.backup
tar xvzf moodle-3.1.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.

chown -R www-data:www-data moodle (Linux debian - change to appropriate user and group for your OS version) chmod -R 755 moodle

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. However, for a simple upgrade, there should be no need to change anything with cron.

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 3.1 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.

If you put your site into Maintenance mode earlier; take it out now!

To do this just go to Administration > 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 Administration > Site administration > Development > Purge all caches) after completing the upgrade on all servers.

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.

After upgrading

The config.php file from your installation should work fine but if you take a look at config-dist.php that came with Moodle 3.0 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 3.0 config-dist.php.

Cron

Cron has received a major update (MDL-25499) and now has support for both scheduled and ad hoc tasks.

The benefits of these changes are:

  • The schedule for every task can be configured by the admin
  • Tasks can run in parallel
  • Cron processes use locking to prevent the same task running at the same time by different processes
  • Clusters with multiple identical application nodes are supported, you can run cron on all of them

A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. To take advantage of the new cron system it is now strongly recommended that administrators increase the frequency that cron is run to at least once per minute.

You also may need to modify any automated scripts you have that are parsing the output from cron. It is no longer possible to simply monitor the output of cron for the string "Cron script completed correctly" (if that is what you were doing). An alternative is to monitor the output for the string "task failed:". If you detect that a task is failing, here are some tips for debugging the failure.

Before the upgrade to 3.1, there may have been a cron task that was failing, which was preventing the rest of cron from being executed. A failure in any single task will no longer prevent the rest of the Moodle cron tasks from executing, so you may uncover previously masked bugs. It is a good idea to closely monitor the output from cron after the upgrade to 3.1.

Assignments

The old assignment (2.2) module has been removed from core and has been replaced by a stub to support transparently remapping URLs and restoring course backups from the old module to the new one.

If you are still using the old assignment (2.2) module, after upgrading to Moodle 3.0 all assignment (2.2) activities will be hidden. You need to run the Assignment upgrade tool to un-hide the activities.

If you really, really need to keep using the old assignment (2.2) module, you should update the code to Moodle 3.0, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.

Possible issues that may affect you in Moodle 3.1

Assignment submission annotation

The Assignment activity can now convert various office document formats to PDF to work with PDF annotations. This is optional - but it requires "unoconv" to be installed and configured on the server. See the Unoconv installation.

Competencies

The new 3.1 feature, Competencies, is enabled by default. It may be disabled by an administrator in Site administration > Competencies.

PHP 5.6 bug

Please note that PHP 5.6 has an upstream bug resulting in some functionality involving AJAX requests to fail on some platforms. It does not affect PHP 5.5 or 7. You need to add always_populate_raw_post_data=-1 to your php.ini. Please refer to documentation.

PHP extension xmlreader requirement

As listed on the Environment page, the PHP extension xmlreader is required (in 3.1 onwards) in order for the downloading of csv, ods, excel etc files in reports and exports to stream progressively.

MySQL full unicode support

In fresh installs of Moodle 3.1.5, MySQL and MariaDB drivers support full UTF-8. For sites upgrading to 3.1.5, a CLI script may be used to convert to full UTF-8. See MySQL full unicode support for details.


See the Moodle 3.1 release notes for the full list of changes in Moodle 3.1.

Moodle 2.8, 2.9 and 3.0 improvements

Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation

See also