Upgrading: diferència entre les revisions

Revisió de 23:38, 2 maig 2013

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.4 in Settings > Site administration > Server > Environment.

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

Check for plugin updates

Check in the Moodle Plugins directory whether there is a 2.4 version available for any contributed/custom plugins (including themes) that you have previously installed on your site. If so, download the plugin code and 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.

Note: If you have any contributed blocks installed, please see below for info about block capabilities undefined.

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:

Moodle software (For example, everything in server/htdocs/moodle)
Moodle uploaded files (For example, server/moodledata)
Moodle database (For example, the SQL or Postgres database)

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.

Install the new Moodle software

Standard install package

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 config.php file back to the new Moodle directory.
As mentioned above, if you had installed any custom plugins on your site you should add them to the new code. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.

Linux

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

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

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

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

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

After upgrading

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

Block capabilities undefined

If you have any contributed/custom blocks installed, after upgrading you may get a debugging message warning you that a block capability has not been defined. For example

The block <blockname> does not define the standard capability block/<blockname>:myaddinstance

In Moodle 2.4, addinstance and myaddinstance capabilities were added for controlling the use of blocks. See the section 'Ready, Set, Go!' in the Blocks dev docs for information on defining these capabilities for any contributed blocks.

Moodle 2.3 improvements

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

@@ Línia 1: / Línia 1: @@
-Система Moodle позволяет обновление от версии к версии. Пожалуйста, для более подробного ознакомления перейдите по ссылкам Upgrading to Moodle 1.6, Upgrading to Moodle 1.8 или Upgrading to Moodle 1.9 для обновляемой версии.
+{{Installing Moodle}}
+''This page explains in detail how to upgrade Moodle. For a summary of the process, see [[Upgrade overview]].''
-Изменения, внесенные в исходный код, такие как установка вспомогательного модуля (не стандартного модуля) или редактирование на сайте php-файла могут не обновиться. Сюда же включаются модификации стандартных тем, которые будут переписаны в процессе обновления.
+==Check the requirements==
-Для использования cpanel можно воспользоваться this tutorial. Не смотря на некоторые неровности по краям и небольшую устарелость, идея должна быть ясна.
+Check that your server meets all requirements for 2.4 in ''Settings > Site administration > Server > [[Environment]]''.
-__TOC__
+Note: You can only upgrade to Moodle 2.4 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.
-Обновляйте версию Moodle по следующим шагам:
+==Check for plugin updates==
-==Проверка системных требований==
+Check in the [http://moodle.org/plugins Moodle Plugins directory] whether there is a 2.4 version available for any contributed/custom plugins (including themes) that you have previously installed on your site. If so, download the plugin code and copy it to the appropriate location in your Moodle code (see [[Installing plugins]]).
-Ознакомтесь с инструкцией по установке и документацией на новую версию. Проверьте системные требования для версии, которую вы хотите обновить на Administration > Server > Environment.
-== Резервирование важных данных ==
+The upgrade of the plugin will then happen as part of the Moodle upgrade process.
-Всегда полезно, хотя и не строго обязательно, делать резервную копию любой системы перед ее серьезным обновлением на случай, если придется вернуться к старой версии. Вообще, очень практично настроить Ваш сервер для ежедневного обновления версии Moodle и просто пропустить этот шаг.
+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.
-Рассмотрим три области, нуждающиеся в резервировании:
+Note: If you have any contributed blocks installed, please see below for info about block capabilities undefined.
-=== 1. Собственно программная директория Moodle ===
+==Before you upgrade your site for real==
-Сделайте отдельную копию этих файлов перед обновлением, что позволит восстановить файл config.php и любые модули, которые были добавлены как темы, языки и т. д.
+'''We advise that you test the upgrade first on a COPY of your production site, to make sure it works as you expect.'''
-=== 2. Ваша папка данных ===
+== Backup important data ==
-Именно сдесь находятся загружаемые данные (такие как ресурсы курса и студенческие задания), так что очень важно иметь резервную копию этих файлов в любом случае. Иногда при обновлении некоторые папки в Вашей директории данных могут исчезнуть или получить другие имена.
+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, the SQL or Postgres database)
-=== 3. Ваша база данных ===
+See [[Site backup]] for more specific information.
-Большинство обновлений Moodle изменяют таблицы баз данных, добавляя или изменяя поля. Существую разные способы резервирования для каждой базы данных. Один из способов резервирования базу данных MySQL состоит в "выгрузке" ее в один SQL-файл. Приведенный ниже пример иллюстрирует Unix команды для загрузки в файл базы данных под названием "moodle":
+==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.
- mysqldump -u username -p -C -Q -e -a moodle > moodle-backup-2007-04-01.sql
-(Ключ "-a" не желателен и должен быть заменен на "--create-options")
-Замените учетную запись в базе данных на имя пользователя. Флаг -p указывает на пароль для пользователя под флагом -u.
-Если хост базы данных отличается от хоста, на котором Вы хотите выполнить команду резервирования (обычно это web-сервер)
-нужно при выполнении дампа MySQL указать его с опцией -h:
- mysqldump -u username -p -h databasehost -C -Q -e -a moodle > moodle-backup-2007-04-01.sql
-Вы также модете воспользоваться функцией экспорта "Export" в опции web-интерфейса Moodle "MySQL Admin" для выполнения этой же операции на любой платформе. В версии Moodle v1.9 и выше эта опция находится в меню '''Site Administration''' -> '''Server''' -> '''Database'''. Этот интерфейс можно также загрузить со страницы http://download.moodle.org/modules/integrations.php. Это компоновка PHPMyAdmin с интерфейсом администратора Moodle.
-==== SQL dump caveats ====
-* Please note that there are a '''LOT''' of 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 ==
-=== 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 custom plugins on your site you should add them to the new code. It is important to check that you get the correct version for your new version of Moodle. Be particularly careful that you do not overwrite any code in the new version of Moodle.
- Linux
+====Linux====
   mv moodle moodle.backup
-  tar xvzf moodle-1.1.tgz
+  tar xvzf moodle-2.4.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 -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.
-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...
+On Linux servers, Moodle 2.4 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.
--rw-r--r--   1 apache system     784 Jun 28  2007 config.php
+== Finishing the upgrade ==
-...lots more lines...
+The last step is to trigger the upgrade processes within Moodle.
-so the owner is apache and the group is system.
+To do this just go to ''Settings > Site administration > Notifications''.
-To replicate this on your new system you can do  'chown apache:system config.php'
+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.
-or to do a whole group do
+Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!
-chown apache:system ./*
-and recursively
-chown -R apache:system ./*
-=== Using CVS ===
-You can use CVS for updating or upgrading your Moodle.
-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!.
-'''For Linux servers'''
+Note: If you are running multiple servers then you should purge all caches manually (via ''Settings > Site administration > Development > Purge all caches'') after completing the upgrade on all servers.
-To do a CVS checkout of Moodle, you first have to logon to the Moodle CVS server.
+==After upgrading==
-  <nowiki>cvs -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle login</nowiki>
+The config.php file from your 2.2 or 2.3 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.4 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.4 config-dist.php.
-  No password for anonymous, so just hit the Enter button.
-Go to the directory where you want the Moodle root to come and type
+==Fatal error: Maximum execution time of 30 seconds exceeded...==
-  <nowiki>cvs -z3 -d:pserver:anonymous@SERVER.cvs.moodle.org:/cvsroot/moodle co -r MOODLE_18_STABLE moodle</nowiki>
+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 .
-  (where MOODLE_18_STABLE is the desired version)
-To update, just go into the Moodle root directory and update to the new files:
+==Possible issues that may affect you in Moodle 2.4==
-  cvs update -dP
+=== Block capabilities undefined ===
-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.
+If you have any contributed/custom blocks installed, after upgrading you may get a debugging message warning you that a block capability has not been defined. For example
-'''For Windows servers'''
+ The block <blockname> does not define the standard capability block/<blockname>:myaddinstance
-You can use Tortoise CVS to do the initial checkout and the updates.
+In Moodle 2.4, ''addinstance'' and ''myaddinstance'' capabilities were added for [[Managing blocks|controlling the use of blocks]]. See the section 'Ready, Set, Go!' in the [[:dev:Blocks|Blocks dev docs]] for information on defining these capabilities for any contributed blocks.
-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.
+=== Moodle 2.3 improvements ===
-Don't forget to visit the admin page after the CVS update process has completed.
+If you are upgrading to Moodle 2.4 from 2.2, please see the section 'Possible issues that may affect you in Moodle 2.3' in the [https://docs.moodle.org/23/en/Upgrading Upgrading to Moodle 2.3 documentation].
-== Finishing the upgrade ==
-The last step is to trigger the upgrade processes within Moodle.
-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.
-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.
-Assuming all goes well (no error messages) then you can start using your new version of Moodle and enjoy the new features!
-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.
-== Verify the upgrade (optional) ==
-If you wish to confirm that the database definitions in the upgraded database match the definitions of a new, clean install (which they should) you might like to look at [[Verify Database Schema]].
-==Upgrading more than one version==
-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.)
 ==See also==
-*[[Installing Moodle]]
+* Using Moodle [http://moodle.org/mod/forum/view.php?id=28 Installation problems forum]
-*[[Installation FAQ]]
+* [[dev:Moodle 2.4 release notes|Moodle 2.4 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]]
 [[fr:Mise à jour]]
-[[ja:アップグレード]]
+[[ja:Moodleをアップグレードする]]
-[[nl:Upgraden]]
+[[de:Aktualisierung von Moodle]]
-[[zh:升级]]
-[[pl:Aktualizacja]]
-[[ru:Обновление]]

Documentation