Hinweis: Sie sind auf den Seiten der Moodle 2.0 Dokumentation. Die Dokumentation der aktuellsten Moodle-Version finden Sie hier: Auf Moodle 2.2 aktualisieren.

Auf Moodle 2.2 aktualisieren: Unterschied zwischen den Versionen

Aus MoodleDocs
Wechseln zu:Navigation, Suche
(Die Seite wurde neu angelegt: „{{Installation}} {{Zum Übersetzen}} en:Upgrading to Moodle 2.2“)
 
Keine Bearbeitungszusammenfassung
Zeile 2: Zeile 2:


{{Zum Übersetzen}}
{{Zum Übersetzen}}
Sie können auf Moodle 2.2. von Moodle 2.1, 2.0 oder 1.9 aktualisieren. Wenn Sie von Moodle 2.0 aktualisieren, lesen Sie bitte auch den Artikel [https://docs.moodle.org/21/de/Auf_Moodle_2.1_aktualisieren Auf Moodle 2.1 aktualisieren]. Wenn Sie von Moodle 1.9 aktualisieren, lesen Sie bitte zusätzlich den Artikel [https://docs.moodle.org/20/de/Auf_Moodle_2.0_aktualisieren Auf Moodle 2.0 aktualisieren]. Danach können Sie direkt auf Moodle 2.2 aktualisieren.
Wenn Sie von einer älteren Moodle-Version aktualisieren, müssen Sie zuerst auf Moodle 1.9.x aktualisieren.
'''Wir empfehlen, die Aktualisierung zuerst auf einer Kopie Ihrer Moodle-Site durchzuführen und zu testen, bevor Sie Ihre Produktiv-Installation aktualisieren.'''
==System-Anforderungen==
* PHP muss mindestens '''5.3.2''' sein
** Erforderliche PHP-Erweiterungen: iconv, curl, ctype, zip, simplexml, spl, pcre, dom, xml, json
** Erforderliche PHP-Einstellung <code>memory_limit</code> mindestens 40MB (64MB oder mehr empfohlen)
* Datenbank:
** MySQL mindestens 5.0.25 (InnoDB Storage Engine dringend empfohlen)
** PostgreSQL mindestens 8.3
** Oracle mindestens 10.2
** MS SQL mindestens 2005
* Browser:
** mindestens Firefox 3
** mindestens Safari 3
** mindestens Google Chrome 4
** mindestens Opera 9
** MS Internet Explorer 7 or later
'''Hinweis''': Diese Anforderungen haben sich seit Moodle 2.1 nicht geändert.
==Vor der Aktualisierung==
'''NOTE''': The upgrade process will irreversibly modify the contents of your database '''and''' your moodledata file storage area. If something goes wrong you '''cannot''' go back. It is vital that you take good backups of both moodledata and the database in case you have problems with the upgrade. If you are not sure how see [[Site backup]] or ask in the moodle.org forums (explaining what your operating system is). 
* Read the [[:dev:Moodle 2.2 release notes|Moodle 2.2 release notes]]  and check the [[:Category:New features|list of new features]]
* Check your site to make sure it meets all system requirements for 2.2 in ''Settings > Site administration > Server > [[Environment]]''
* '''Do a full database backup!'''
* '''Do a full moodledata backup'''
* '''Check your backups carefully'''
* Remember to purge PHP cache if using any PHP accelerator
==Possible issues that may affect you==
* If you have custom reports, there have been changes that may require (simple) changes to be made to their code. See the developer documentation [[:dev:General report plugins]] for details.
* Global search has been removed from core as it was broken.  (A new global search is being written for 2.3.)
* Some web service functions have been deprecated.  They still work, but check any web service connections you may have to your Moodle for the future.
==Checking database schema - old sites==
If your Moodle site has been upgraded through many prior versions it is possible that there will be some problems with the database schema (compared to a fresh 2.0 installation). This may cause the upgrade to fail. If your site started life prior to Moodle 2.0 it is a very good idea to check and correct the database schema before upgrading. See [[Verify Database Schema]]. You should also run the database integrity checks in the XMLDB editor, see the 'See also' for a link to extra scripts to check for other discrepancies.
==Now upgrade==
Once you have satisfied the requirements for Moodle 2.2, follow the instructions on the [[Upgrading|upgrading]] page.
On Linux servers, Moodle 2.2 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.
==After upgrade==
The config.php file from your 2.0 installation should work fine but if you take a look at config-dist.php that came with Moodle 2.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 2.2 config-dist.php.
==Siehe auch==
* [[dev:Moodle 2.2 release notes|Moodle 2.2 Release Notes]]


[[en:Upgrading to Moodle 2.2]]
[[en:Upgrading to Moodle 2.2]]

Version vom 25. Mai 2012, 10:35 Uhr


Baustelle.png Diese Seite ist noch nicht vollständig übersetzt.

Sie können auf Moodle 2.2. von Moodle 2.1, 2.0 oder 1.9 aktualisieren. Wenn Sie von Moodle 2.0 aktualisieren, lesen Sie bitte auch den Artikel Auf Moodle 2.1 aktualisieren. Wenn Sie von Moodle 1.9 aktualisieren, lesen Sie bitte zusätzlich den Artikel Auf Moodle 2.0 aktualisieren. Danach können Sie direkt auf Moodle 2.2 aktualisieren.

Wenn Sie von einer älteren Moodle-Version aktualisieren, müssen Sie zuerst auf Moodle 1.9.x aktualisieren.

Wir empfehlen, die Aktualisierung zuerst auf einer Kopie Ihrer Moodle-Site durchzuführen und zu testen, bevor Sie Ihre Produktiv-Installation aktualisieren.

System-Anforderungen

  • PHP muss mindestens 5.3.2 sein
    • Erforderliche PHP-Erweiterungen: iconv, curl, ctype, zip, simplexml, spl, pcre, dom, xml, json
    • Erforderliche PHP-Einstellung memory_limit mindestens 40MB (64MB oder mehr empfohlen)
  • Datenbank:
    • MySQL mindestens 5.0.25 (InnoDB Storage Engine dringend empfohlen)
    • PostgreSQL mindestens 8.3
    • Oracle mindestens 10.2
    • MS SQL mindestens 2005
  • Browser:
    • mindestens Firefox 3
    • mindestens Safari 3
    • mindestens Google Chrome 4
    • mindestens Opera 9
    • MS Internet Explorer 7 or later

Hinweis: Diese Anforderungen haben sich seit Moodle 2.1 nicht geändert.

Vor der Aktualisierung

NOTE: The upgrade process will irreversibly modify the contents of your database and your moodledata file storage area. If something goes wrong you cannot go back. It is vital that you take good backups of both moodledata and the database in case you have problems with the upgrade. If you are not sure how see Site backup or ask in the moodle.org forums (explaining what your operating system is).

  • Read the Moodle 2.2 release notes and check the list of new features
  • Check your site to make sure it meets all system requirements for 2.2 in Settings > Site administration > Server > Environment
  • Do a full database backup!
  • Do a full moodledata backup
  • Check your backups carefully
  • Remember to purge PHP cache if using any PHP accelerator

Possible issues that may affect you

  • If you have custom reports, there have been changes that may require (simple) changes to be made to their code. See the developer documentation dev:General report plugins for details.
  • Global search has been removed from core as it was broken. (A new global search is being written for 2.3.)
  • Some web service functions have been deprecated. They still work, but check any web service connections you may have to your Moodle for the future.

Checking database schema - old sites

If your Moodle site has been upgraded through many prior versions it is possible that there will be some problems with the database schema (compared to a fresh 2.0 installation). This may cause the upgrade to fail. If your site started life prior to Moodle 2.0 it is a very good idea to check and correct the database schema before upgrading. See Verify Database Schema. You should also run the database integrity checks in the XMLDB editor, see the 'See also' for a link to extra scripts to check for other discrepancies.

Now upgrade

Once you have satisfied the requirements for Moodle 2.2, follow the instructions on the upgrading page.

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

After upgrade

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

Siehe auch