Upgrading: Difference between revisions

From MoodleDocs
Main page ► Installation ► Upgrading
Installation
(MDL-48766 Geoip lookups using new maxmind database)
(→‎Course section pages: The general section no longer appears above the selected section.)
 
(164 intermediate revisions by 20 users not shown)
Line 1: Line 1:
{{Installing Moodle}}
{{Installing Moodle}}
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''
''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''
==Check the requirements==
==Check the requirements==
Before upgrading, check that your server meets all requirements for {{Version}} in ''Site administration > Server > [[Environment]]''.


Check that your server meets all requirements for {{Version}} in ''Administration > Site administration > Server > [[Environment]]''.
See the [{{Release notes}} Moodle {{Version}} release notes] for server and client software requirements.
 
Moodle 3.2 has raised the minimum required PHP version to 5.6.5.
 
Note: You can only upgrade to Moodle {{Version}} 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.


Notes:
* You can only upgrade to Moodle {{Version}} from Moodle 4.1.2 or later. If upgrading from earlier versions, you must [https://docs.moodle.org/401/en/Upgrading upgrade to 4.1.2] as a first step.
==Before upgrading==
==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.'''
'''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|upgrade key]] for your site.
Consider setting the [[Upgrade key|upgrade key]] for your site.
== Backup important data ==
== Backup important data ==
There are three areas that should be backed up before any upgrade:
There are three areas that should be backed up before any upgrade:
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle software (For example, everything in server/htdocs/moodle)
#Moodle uploaded files (For example, server/moodledata)
#Moodle uploaded files (For example, server/moodledata)
#Moodle database (For example, your Postgres or MySQL database dump)
#Moodle database (For example, your Postgres or MySQL database dump)
See [[Site backup]] for more specific information.
See [[Site backup]] for more specific information.
== Check for plugin updates ==
== 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 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.


Line 34: Line 26:


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.
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==
==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.
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 version of the software through
You can download the latest release from [https://download.moodle.org/ Moodle downloads].
 
wget http://sourceforge.net/projects/moodle/files/Moodle/stable{{Version2}}/moodle-latest-{{Version2}}.tgz
 
=== Standard install package ===
=== Standard install package ===
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
# 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.
# 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.  
# 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.)
# 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.
# 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-{{Version}}.tgz
  tar xvzf moodle-latest-{{Version}}.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'''):
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
  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. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet.  
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 root:root moodle (Linux debian - or even create a user especially for moodle. '''Don't''' use the web server user, e.g. www-data)
 
chmod -R 755 moodle
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:  
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)
  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. However, for a simple upgrade, there should be no need to change anything with cron.
if necessary. However, for a simple upgrade, there should be no need to change anything with cron.
 
=== Using Git ===
=== Using Git ===
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.
===Command line upgrade===
===Command line upgrade===
On Linux servers, Moodle {{Version}} 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.
On Linux servers, Moodle {{Version}} 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 ==
== Finishing the upgrade ==
The last step is to trigger the upgrade processes within Moodle.  
The last step is to trigger the upgrade processes within Moodle.  


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


To do this just go to ''Administration > Site administration > Notifications''.
To do this just go to ''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.
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.
Line 91: Line 65:
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!
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.
Note: If you are running multiple servers then you should purge all caches manually (via ''Site administration > Development > Purge all caches'') after completing the upgrade on all servers.
 
===Fatal error: Maximum execution time of 30 seconds exceeded...===
===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 successful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.


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 {{Version}}==


==After upgrading==
===New activity icons===


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.
Updated activity icons 24 x 24px are outlined with a transparent background and use an accessible colour palette.


===Cron===
===Course section pages===
 
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, [[Cron#Debugging_Scheduled_Tasks|here]] are some tips for debugging the failure.
 
Before the upgrade, 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.
 
===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 {{Version}}==


''Please add items here...'' See the [https://tracker.moodle.org/issues/?jql=labels%20%3D%20upgrade_notes%20and%20fixVersion%3D3.2 list of upgrade_notes-labelled issues].
A new section page displays the contents of an individual course section. The general section no longer appears above the selected section. Section names in the course page link to section pages. Any manually added section links of the form course/view.php?id=xx#section-z will continue working, linking to course page anchors.


===Custom roles requiring site administration access===
===Manual enrolment course welcome message===


Any custom roles which require access to any part of site administration that do not use the manager archetype will need to be allowed the new capability, [[Capabilities/moodle/site:configview|moodle/site:configview]].
As for self enrolment, a course welcome message can be sent for [[Manual enrolment]]. An admin or manager can customise the message in the manual enrolment settings in the course.


===Removed plugins===
===New notifications===


If you use any of these plugins you need to download them during upgrade:
* [[Self enrolment]]: Users are notified before they are unenrolled due to inactivity
* Tasks: Administrators are notified when tasks fail


[https://github.com/moodlehq/moodle-auth_radius RADIUS] authentication plugin is using the mcrypt PHP functions which are deprecated as of PHP 7.1. Thus the plugin has been removed from the standard Moodle 3.2 package.
===TinyMCE is the default text editor===


The [https://github.com/moodlehq/moodle-repository_alfresco Alfresco] repository plugin does not work with Alfresco 5.0.c or later and so has been removed from the standard Moodle 3.2 package.
[[TinyMCE]] becomes the default text editor of sites upgrading to 4.4. Since 4.2 it has been the default text editor of new installs.


Themes [https://moodle.org/plugins/theme_base Base] and [https://moodle.org/plugins/theme_canvas Canvas] have been deprecated and also removed from the standard Moodle 3.2 package. These themes can not be used by themselves but they may be used as parent themes.
===Topics course format renamed===


===Outgoing mail setup===
The Topics course format is renamed 'Custom sections' and new sections are no longer numbered.


Make sure to visit Site administration > Server > Email > Outgoing mail configuration. There is no longer setting "Always send from no-reply address", instead there is a setting "Allowed email domains". If you want to send emails from users real addresses you need to add domains allowed by your mail server to this list. Sending email from email addresses not matching sender domain will be detected by clients and such emails could be classified as "Spam". '''Moodle will no longer use support email as Return-Path.'''
===BigBlueButton credentials required===


===Recommendations on changing settings===
To continue using the [[BigBlueButton]] free tier hosting, the admin needs to register with BigBlueButton to obtain credentials for their site.


Some administrative settings and roles have changed their defaults in Moodle 3.2. These changes will not be automatically applied to the upgraded sites, however we recommend you to change them manually to improve security, user experience and navigation:
===Chat and Survey activities===


* Site administration > Appearance > Navigation : Show my course categories (navshowmycoursecategories). Set this to off if you use theme with flat navigation like Boost.
[[Chat]] and [[Survey]] activities are disabled in new Moodle 4.4 installs and are due for removal in Moodle 4.5. You can check if they are used on your upgraded site in ''Site administration > Plugins > Manage activities'' and disable them if they are unused.
* Site administration > Grades > General settings : Navigation method (grade_navmethod). New default value - "Tabs". This improves navigation especially in Boost theme where "Administration" block is not available.
* Site administration > Appearance > Navigation : Link admin categories (linkadmincategories). New default value - "Yes". This improves navigation especially in Boost theme where "Administration" block is not available.
* Site administration > Security > HTTP security : cURL blocked hosts list (curlsecurityblockedhosts) and cURL allowed ports list (curlsecurityallowedport). These are two new settings improving security of cURL requests (used in blogs, URL repository, etc.). We
recommend to blacklist localhost and its aliases and allow only 80 port.
* Site administration > Courses > Course default settings : Default value for "Format" (moodlecourse/format) was changed from Weeks to Topics. Default value for "Number of sections" (moodlecourse/numsections) was changed from 10 to 4.


===Asynchronous activity deletion with Recycle bin===
===Multi-factor authentication SMS factor===


Recycle bin that was added in Moodle 3.1 and automatically enabled has been found to cause slowness during activity deletion. Since Moodle 3.2 enabling recycle bin automatically means that activity deletion will happen asynchronously in the background. You must ensure that cron runs regularly, preferably every minute. Running cron every minute will '''not''' slow down the site because each task will still run only when scheduled.
To increase site security, [[Multi-factor authentication]] includes the option to authenticate via an SMS code.


===Media players===
===Option to show password as plain text===


New "Media players" plugin type was introduced in Moodle 3.2. Previously media players may have been overridden by themes. This will no longer work, instead you need to create [https://docs.moodle.org/dev/Media_players media player plugins]. We have also added and automatically enabled Video.JS as the default video and audio player. If you had filters with media players installed they may no longer be needed in Moodle 3.2.
You can allow users to show their entered password as plain text via a new setting 'Password visibility toggle' in ''Site administration > Plugins > [[Manage authentication]]''. The option is disabled on upgraded sites and set to 'Small screens only' on new installs.


Media players [https://github.com/moodlehq/moodle-media_flowplayerflash Flowplayer], [https://github.com/moodlehq/moodle-media_wmp Windows media player], [https://github.com/moodlehq/moodle-media_realplayer RealPlayer] and [https://github.com/moodlehq/moodle-media_quicktime Quicktime] were present in Moodle 3.1 but removed in 3.2. If they are needed they should be installed in media/player directory. Please note that Video.JS has built-in Flash player and you should no longer need Flowplayer. Other three players were removed because these formats are extremely rare in the modern world and most browsers don't support them anyway.
===Browse list of users page improvements===


Site administration > Users > Browse list of users no longer shows the fields 'City' and 'Country' unless they are included as identity fields.


See the [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]] for the full list of changes in Moodle {{Version}}.
===Asynchronous course backups===


===Customised MathJax URL===
Asynchronous backups provide a better user experience allowing users to do other operations while a backup or restore is in progress. Asynchronous course backups are enabled for new Moodle 4.4 installs. You can enable asynchronous course backups on your upgraded site in ''Site administration > Courses > Asynchronous backup/restore''.


If you customised the mathjax CDN url note that filter_mathjaxloader/httpurl has been removed and only filter_mathjaxloader/httpsurl is used.
===Theme settings===


=== IP address lookups ===
In ''Site administration > Appearance'', Theme settings are renamed 'Advanced theme settings'. Settings for Boost or Classic are accessed via the 'Edit theme settings' link in ''Site administration > Appearance > Themes''.


Moodle now supports looking up IPv6 addresses using the [http://dev.maxmind.com/geoip/geoip2/geolite2/ GeoLite2]  database from [http://www.maxmind.com Maxmind]. This replaces the existing GeoLite legacy database used in previous versions and the new GeoIP2 database will need to be installed to use this functionality.


=== Moodle 2.9, 3.0 and 3.1 improvements ===
See also the list of [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.4%20AND%20labels%20%3D%20upgrade_notes upgrade_notes-labelled issues] and [https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%204.4%20AND%20labels%20%3D%20ui_change ui_change-labelled issues] also the [https://moodledev.io/docs/4.4/devupdate Moodle 4.4 developer update].


Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation
===New capabilities in Moodle {{Version}}===


* [https://docs.moodle.org/29/en/Upgrading Upgrading to Moodle 2.9]
* View all custom reports (moodle/reportbuilder:viewall)
* [https://docs.moodle.org/30/en/Upgrading Upgrading to Moodle 3.0]
* Access TinyMCE Premium features (tiny/premium:accesspremium)
* [https://docs.moodle.org/31/en/Upgrading Upgrading to Moodle 3.1]
* Use upload course tool (tool/uploadcourse:use)


==See also==
== Moodle 4.1, 4.2 and 4.3 upgrading notes ==
Depending on which version you are upgrading from, please see the section 'Possible issues that may affect you' in the documentation:
* [https://docs.moodle.org/401/en/Upgrading Upgrading to Moodle 4.1]
* [https://docs.moodle.org/402/en/Upgrading Upgrading to Moodle 4.2]
* [https://docs.moodle.org/403/en/Upgrading Upgrading to Moodle 4.3]


* [[Installation]]
==Any questions about the process?==
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation help forum]  
Please post in the [https://moodle.org/mod/forum/view.php?id=28 Installing and upgrading help forum] on moodle.org.
* [[dev:Moodle {{Version}} release notes|Moodle {{Version}} release notes]]


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

Latest revision as of 06:18, 30 April 2024

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

Check the requirements

Before upgrading, check that your server meets all requirements for 4.4 in Site administration > Server > Environment.

See the Moodle 4.4 release notes for server and client software requirements.

Notes:

  • You can only upgrade to Moodle 4.4 from Moodle 4.1.2 or later. If upgrading from earlier versions, you must upgrade to 4.1.2 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 4.4 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 download the latest release from Moodle downloads.

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-latest-4.4.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. For maximum security the files should not be writeable by your server. This is especially important on a 'production' server open to the public internet. 

chown -R root:root moodle (Linux debian - or even create a user especially for moodle. Don't use the web server user, e.g. www-data)
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 4.4 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 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 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 successful upgrade. See the forum discussion at https://moodle.org/mod/forum/discuss.php?d=119598.

Possible issues that may affect you in Moodle 4.4

New activity icons

Updated activity icons 24 x 24px are outlined with a transparent background and use an accessible colour palette.

Course section pages

A new section page displays the contents of an individual course section. The general section no longer appears above the selected section. Section names in the course page link to section pages. Any manually added section links of the form course/view.php?id=xx#section-z will continue working, linking to course page anchors.

Manual enrolment course welcome message

As for self enrolment, a course welcome message can be sent for Manual enrolment. An admin or manager can customise the message in the manual enrolment settings in the course.

New notifications

  • Self enrolment: Users are notified before they are unenrolled due to inactivity
  • Tasks: Administrators are notified when tasks fail

TinyMCE is the default text editor

TinyMCE becomes the default text editor of sites upgrading to 4.4. Since 4.2 it has been the default text editor of new installs.

Topics course format renamed

The Topics course format is renamed 'Custom sections' and new sections are no longer numbered.

BigBlueButton credentials required

To continue using the BigBlueButton free tier hosting, the admin needs to register with BigBlueButton to obtain credentials for their site.

Chat and Survey activities

Chat and Survey activities are disabled in new Moodle 4.4 installs and are due for removal in Moodle 4.5. You can check if they are used on your upgraded site in Site administration > Plugins > Manage activities and disable them if they are unused.

Multi-factor authentication SMS factor

To increase site security, Multi-factor authentication includes the option to authenticate via an SMS code.

Option to show password as plain text

You can allow users to show their entered password as plain text via a new setting 'Password visibility toggle' in Site administration > Plugins > Manage authentication. The option is disabled on upgraded sites and set to 'Small screens only' on new installs.

Browse list of users page improvements

Site administration > Users > Browse list of users no longer shows the fields 'City' and 'Country' unless they are included as identity fields.

Asynchronous course backups

Asynchronous backups provide a better user experience allowing users to do other operations while a backup or restore is in progress. Asynchronous course backups are enabled for new Moodle 4.4 installs. You can enable asynchronous course backups on your upgraded site in Site administration > Courses > Asynchronous backup/restore.

Theme settings

In Site administration > Appearance, Theme settings are renamed 'Advanced theme settings'. Settings for Boost or Classic are accessed via the 'Edit theme settings' link in Site administration > Appearance > Themes.


See also the list of upgrade_notes-labelled issues and ui_change-labelled issues also the Moodle 4.4 developer update.

New capabilities in Moodle 4.4

  • View all custom reports (moodle/reportbuilder:viewall)
  • Access TinyMCE Premium features (tiny/premium:accesspremium)
  • Use upload course tool (tool/uploadcourse:use)

Moodle 4.1, 4.2 and 4.3 upgrading notes

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

Any questions about the process?

Please post in the Installing and upgrading help forum on moodle.org.

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