Note: You are currently viewing documentation for Moodle 2.6. 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
(→‎For Windows servers: think this is right)
(→‎Possible issues that may affect you in Moodle 2.6: MySQL dmlwriteexception error when using calculated questions in a quiz (MDL-29332))
 
(118 intermediate revisions by 35 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.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==


For those using cpanel, you can use [http://ic.eflclasses.org/tutorials/howtoupgrademoodlewithcpanel.swf this tutorial]. It is a bit rough around the edges and is a little dated, but you should get the idea.
Check that your server meets all requirements for 2.6 in ''Administration > Site administration > Server > [[Environment]]''.


New in Moodle 2.6 is the php_setting [[OPcache]].


__TOC__
Note: You can only upgrade to Moodle 2.6 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.


When upgrading a Moodle installation you should follow these steps:
==Before you upgrade your site for real==


==Check the requirements==
'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''
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 ''Administration > Server > [[Environment]]''.


== Backup important data ==
== Backup important data ==
There are three areas that need backing up:
#Moodle software directory/folder (For example, everything in server/htdocs/moodle)
#Moodle data (For example, server/moodledata)
#Moodle SQL 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 issue. 
:''TIP:'' One more time, "do not risk what you can not afford to lose": do regular backups, make sure it backed up and know how to restore it!
=== Moodle software directory ===
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, and languages.
The best way is to rename the current Moodle directory to something else, then unpack the new Moodle archive into the old location.


=== Moodle data directory ===
There are three areas that should be backed up before any upgrade:
The default name for this folder is moodledata. This is where uploaded content resides (such as course resources and student assignments). It is very important to have a backup of these files on a regular basis as a best practice. Sometimes upgrades may move or rename directories within your data directory.
#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)


=== SQL database ===
See [[Site backup]] for more specific information.
Most Moodle upgrades will alter the SQL database tables, adding or changing fields. Each SQL server program (for example,MySQL, Postgresql, Oracle) has different ways to backup. In a MySQL server, one way of backing up is to 'dump' it to a single SQL file. The following example shows Unix commands to dump the database called "moodle":


mysqldump -u username -p -C -Q -e -a moodle > moodle-backup-2007-04-01.sql
==Put your site into maintenance mode==
(The "-a" switch is deprecated and should be replaced by "--create-options")
Before you begin upgrading your site, you should put it into [[Maintenance_mode | maintenance mode]] to stop any non-admin users from logging in.


Substitute your database user account for username. The -p flag will prompt you for the password for the username specified by -u.
== Check for add-on updates ==


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


mysqldump -u username -p -h databasehost -C -Q -e -a moodle > moodle-backup-2007-04-01.sql
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.6 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]]).


You can also use the "Export" feature in Moodle's optional "MySQL Admin" web interface to do the same thing on all platforms. In Moodle v1.9 and greater, this is located in '''Site Administration''' -> '''Server''' -> '''Database'''. This interface can also be downloaded from http://download.moodle.org/modules/integrations.php. It is an integration of PHPMyAdmin for the Moodle administration interface.
The upgrade of the add-on will then happen as part of the Moodle upgrade process.


==== SQL dump caveats ====
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.
There are a '''MANY''' options possible for mysqldump.
*Please talk with your Systems Administrator (if you have one) or similar to see if there are site-specific flags you should use for your SQL dump.
** For example, if your local installation is running MySQL 5.2 and you are moving to a system running MySQL 5.0 or 4.1, you really ought to use the "--compat=mysql40" flag. (This is not too uncommon of a situation given the nature of ISP hosting as compared to local user Moodle setups)
* This seems obvious, but should be said outright: These instructions only work for dumping from MySQL! Postgresql, Oracle, and other database servers have different tools to dump databases.
* Given the example mysql import lines, above, you really should use the --no-create-db flag. If your database locally is named something differently from the migration site, not including this flag could cause problems.


== 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 1.x.1 to 1.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.
*Unzip or unpack the upgrade file so that all the Moodle software program files are overwritten on the server.  Moodle will adjust SQL and moodledata if it needs to in the upgrade.
*Use the notification link in the site administration to start the upgrade process. You will see a series of lines indicating progress. 
*After a successful upgrade, turn off the maintenance mode for your users.


=== Using a downloaded archive ===
# Move your old Moodle software program files to another location. ''Do NOT copy new files over the old files.''
*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.
# 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 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.
# Dont forget to also copy over your moodledata folder / directory.  If you don't you will get a "fatal error $cfg- dataroot is not configured properly".


====Linux====
====Linux====
Linux
  mv moodle moodle.backup
  mv moodle moodle.backup
  tar xvzf moodle-1.1.tgz
  tar xvzf moodle-2.6.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  
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:
  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.
if necessary.


where www-data is whatever user the Apache user is on your system. This is often 'apache' or 'www'.
=== Using Git ===
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
You can use Git for updating or upgrading your Moodle. See [[Git for Administrators]] for details.


ls -l
===Command line upgrade===
...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.  
On Linux servers, Moodle 2.6 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.


To replicate this on your new system you can do  'chown apache:system config.php'
== Finishing the upgrade ==


or to do a whole group do
The last step is to trigger the upgrade processes within Moodle.


chown apache:system ./*
To do this just go to ''Administration > Site administration > Notifications''.


and recursively
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.


chown -R apache:system ./*
Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!


=== Using CVS ===
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.


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 2.6 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.6 config-dist.php.


====For Linux servers====
==Fatal error: Maximum execution time of 30 seconds exceeded...==


To do a CVS checkout of Moodle, you first have to logon to the Moodle CVS server.
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 .


  <nowiki>cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login</nowiki>
==Possible issues that may affect you in Moodle 2.6==
  No password for anonymous, so just hit the Enter button.
===Ghostscript===
For the new Annotate PDF assignment feature to work properly, Ghostscript needs to be installed on your server. Check the path from ''Site administration > Plugins > Activity modules > Assignment > Feedback plugins >Annotate PDF''. (Note that if is not enabled or the path is not correct, then the link 'Launch PDF editor' will not appear for teachers when grading PDF assignments.)


Go to the directory where you want the Moodle root to come and type
===New Box.net API===


  <nowiki>cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -r MOODLE_18_STABLE moodle</nowiki>
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.
  (where MOODLE_18_STABLE is the desired version)


To update, just go into the Moodle root directory and update to the new files:
Box.net repository users will no longer be possible to create a shortcut/alias to a file stored in Box.net.


  cvs update -dP
'''IMPORTANT''': The Box.net-alias-to-copy-conversion tool should be run ''as soon as possible''. See [[Box.net APIv1 migration]] for details.
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.
===Theme compatibility===


====For Windows servers====
If your site has a custom theme, then you might run into an error during upgrade "Debug info: Unknown column 'cacherev' in 'field list'".


You can use Tortoise CVS to do the initial checkout and the updates.
The solution is to temporarily switch your theme to "standard" theme during the upgrade.  You can do this by adding "theme=standard" on the URL or by adding this to your Moodle config.php:


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.
$CFG->theme = "standard";


Do not forget to trigger the install process in the site administration block (see below).
After upgrade your theme might still work fine.


== Finishing the upgrade ==
Another solution is to complete your upgrade via a CLI.


The last step is to trigger the upgrade processes within Moodle.
===My Mobile theme removal===


To do this just visit the admin page of your installation e.g. ''<nowiki>http://example.com/moodle/admin</nowiki>''
The "My Mobile" theme has been removed from Moodle 2.6 (MDL-40874). During the upgrade process, the theme will be uninstalled and all its settings will be deleted. The "My Mobile" theme and its extending themes will fall back to the mobile friendly "Clean" theme.


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.
To keep the "My Mobile" theme and its settings, BEFORE UPGRADING files from the unmaintained plugin must be copied into theme/mymobile. The unmaintained plugin can be downloaded from the [https://moodle.org/plugins/view.php?plugin=theme_mymobile MyMobile theme entry in the plugins directory].


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.
===Backup and restore of assignments from Moodle 2.2 and older===


Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!
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.6. See the section 'Restoring course backups from Moodle 2.2 and older' in [[Assignment upgrade tool]] for details of what to do.


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.
===MySQL dmlwriteexception error when using calculated questions in a quiz===


== Verify the upgrade (optional) ==
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.


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]].
=== Moodle 2.3, 2.4 and 2.5 improvements ===


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


In general, it is recommended to upgrade via each version of Moodle, for example 1.7 -> 1.8 -> 1.9. An exception to this is when upgrading from 1.5 or 1.6, when it is recommended that 1.7 is skipped, in other words upgrade 1.5 -> 1.6 -> 1.8 -> 1.9. (The main reason for this recommendation is that the default roles settings obtained when upgrading to 1.7 are not ideal for 1.8 onwards.)
* [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3]
* [https://docs.moodle.org/24/en/Upgrading Upgrading to Moodle 2.4]
* [https://docs.moodle.org/25/en/Upgrading Upgrading to Moodle 2.5]


==See also==
==See also==


*[[Installing Moodle]]
* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]  
*[[Installation FAQ]]
* [[dev:Moodle 2.6 release notes|Moodle 2.6 release notes]]
*[[Upgrading to Moodle 1.6]]
* [[dev:Upgrade API|Upgrade API]]
*[[Upgrading to Moodle 1.8]]
*[[Upgrading to Moodle 1.9]]
*[[Upgrading to Moodle 2.0]]
*[[Environment]]
*Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems] forum
*[http://otaru-jc.ac.jp/hagley/howtoupgrademoodlewithcpanel.swf How to upgrade Moodle with cpanel tutorial]
 
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]
*[http://moodle.org/mod/forum/discuss.php?d=104887 Best practices for QA]
 
[[Category:Installation]]
 


[[es:Actualización de moodle]]
[[es:Actualización de moodle]]
[[fr:Mise à jour]]
[[fr:Mise à jour]]
[[ja:アップグレード]]
[[ja:Moodleをアップグレードする]]
[[nl:Upgraden]]
[[zh:升级]]
[[pl:Aktualizacja]]
[[de:Aktualisierung von Moodle]]
[[de:Aktualisierung von Moodle]]

Latest revision as of 09:36, 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.6 in Administration > Site administration > Server > Environment.

New in Moodle 2.6 is the php_setting OPcache.

Note: You can only upgrade to Moodle 2.6 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.6 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.
  5. Dont forget to also copy over your moodledata folder / directory. If you don't you will get a "fatal error $cfg- dataroot is not configured properly".

Linux

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

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 2.6 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.6 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.6

Ghostscript

For the new Annotate PDF assignment feature to work properly, Ghostscript needs to be installed on your server. Check the path from Site administration > Plugins > Activity modules > Assignment > Feedback plugins >Annotate PDF. (Note that if is not enabled or the path is not correct, then the link 'Launch PDF editor' will not appear for teachers when grading PDF assignments.)

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.

Theme compatibility

If your site has a custom theme, then you might run into an error during upgrade "Debug info: Unknown column 'cacherev' in 'field list'".

The solution is to temporarily switch your theme to "standard" theme during the upgrade. You can do this by adding "theme=standard" on the URL or by adding this to your Moodle config.php: 

$CFG->theme = "standard";

After upgrade your theme might still work fine.

Another solution is to complete your upgrade via a CLI.

My Mobile theme removal

The "My Mobile" theme has been removed from Moodle 2.6 (MDL-40874). During the upgrade process, the theme will be uninstalled and all its settings will be deleted. The "My Mobile" theme and its extending themes will fall back to the mobile friendly "Clean" theme.

To keep the "My Mobile" theme and its settings, BEFORE UPGRADING files from the unmaintained plugin must be copied into theme/mymobile. The unmaintained plugin can be downloaded from the MyMobile theme entry in the plugins directory.

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.6. 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, 2.4 and 2.5 improvements

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

See also

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