View source for Manual:Upgrading/de-formal

<languages/>
{{MW quick download|align={{dir|{{PAGELANGUAGE}}|left|right}}}}

<span id="Basic_overview"></span>
== Übersicht ==

<span id="File_transfer"></span>
=== Dateiübertragung ===

Eine Methode zur Übertragung der Dateien auswählen:

* [[w:de:Wget|wget]]
* Secure copy (sicheres Kopieren) mit [https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html SCP] oder [[w:de:WinSCP|WinSCP]]
* [[w:de:SSH File Transfer Protocol|SSH File Transfer Protocol]] (SFTP)
* Einen [[w:de:File Transfer Protocol|FTP]]-Client verwenden.
* Möglicherweise bietet Ihnen Ihr Provider einen Dateimanager als webbasierte Benutzeroberfläche an.
* Irgendeine andere Methode. <span lang="en" dir="ltr" class="mw-content-ltr">There is a list of these at [[w:Comparison of file transfer protocols|Comparison of file transfer protocols]]</span>

<span id="Preliminary"></span>
===Vorbereitung===

Lesen Sie die {{git file|project=mediawiki/core|branch={{MW stable release git}}|file=UPGRADE|text=UPGRADE Textdatei, die in MediaWiki enthalten ist}}.

# Überprüfen Sie die Voraussetzungen
# Lesen Sie die RELEASE-NOTES-Datei
# Lesen Sie die UPGRADE-Datei
# Sichern Sie die vorhandenen Dateien und die Datenbank
# Entpacken Sie die neuen Dateien
# Aktualisierung der Erweiterungen
# Starten Sie das Update-Skript, um die Datenbank zu überprüfen.
# Testen Sie das Update.
# Entfernen der Überreste der alten Installationen

<span id="Check_requirements"></span>
== Überprüfen Sie die Anforderungen == 
{{Security warning 2021-12}}
{{Warning|Do not upgrade from a MediaWiki version older than 1.33 to MediaWiki 1.39.1, or you may lose data! Upgrade to {{ll|MediaWiki 1.35}} first. See {{phab|T326071}}.}}
MediaWiki {{MW stable branch number}} erfordert:

* '''PHP {{MW stable php requirement}}'''+
* Eines der folgenden:
** '''MariaDB {{MW stable MariaDB requirement}}'''+
** '''MySQL {{MW stable mysql requirement}}'''+
** '''PostgreSQL {{MW stable postgresql requirement}}'''+
** '''SQLite {{MW stable sqlite requirement}}'''+

{{Upgrades from older versions}}

Wenn Sie PostgreSQL benutzen, lesen Sie bitte auch {{ll|Manual:Upgrading Postgres}}.

Für weitere Informationen lesen Sie bitte {{ll|Manual:Installation requirements}} und {{ll|Compatibility}}.

<span id="Read_the_release_notes"></span>
== Lesen Sie die Versionshinweise ==
In der "Tarball-Distribution" (der .tar-Paket-Datei) oder unter den von [[Special:MyLanguage/Gerrit|Git]] ausgecheckten/exportierten Dateien gibt es eine Reihe von Dateien mit Großbuchstaben in den Dateinamen, von denen eine die '''{{git file|project=mediawiki/core|branch={{MW stable branch git}}|file=RELEASE-NOTES-{{MW stable branch number}}|text=RELEASE-NOTES}}''' ([[Special:MyLanguage/Release notes|wiki]]) enthält.
Öffnen Sie diese jetzt und finden Sie heraus, was in diesem Release geändert wurde.
Auch die Anweisungen in der UPGRADE-Datei sollten beachtet werden.

<span id="Clear_pending_jobs"></span>
== Ausstehende Aufträge löschen ==
Aus Performance-Gründen verzögern sich einige Aktionen in der Datenbank und werden vom [[Special:MyLanguage/Manual:Job queue|job queue]] verwaltet.
Diese Aufträge werden in der Datenbank gespeichert und enthalten Parameter mit Informationen über Aktionen, die sie ausführen sollen.
Es wird dringend empfohlen, diese ausstehenden Jobs vor dem Upgrade des Wikis auszuführen, um zu vermeiden, dass sie fehlschlagen, falls sich die Parameterspezifikation dieser Jobs mit der neuen Version ändert.
Verwenden Sie {{ll|Manual:RunJobs.php|runJobs.php}}, um alle ausstehenden Aufträge auszuführen und die Warteschlange zu löschen, bevor Sie das Upgrade durchführen.

<span id="Back_up_existing_files_and_the_database"></span>
== Sichern vorhandener Dateien und der Datenbank ==

:''Vollständige Anleitung: {{ll|Manual:Backing up a wiki}}''

Während die Upgrade-Skripte gut in Stand gehalten und robust sind, können dennoch Dinge schief gehen. Bevor Sie das Datenbank-Schema aktualisieren, ""machen Sie ein vollständiges [[Special:MyLanguage/Manual:Backing up a wiki|Backup]]"" Ihres Wiki, inklusive der Datenbank und den Dateien:

* der Inhalt deines Wikis, von der Datenbank (stellen Sie sicher, den richtigen Zeichensatz zu haben, überprüfen Sie dies zuerst in der LocalSettings.php). Es wäre auch gut, zu dem SQL-Datenbank-Dump zusätzlich einen XML-Dump zu erstellen.
:* Bei MySQL ist für einen SQL- bzw. XML-Dump der  <code>mysql</code> Befehl zu verwenden:
 mysqldump --user='''''wikidb_user''''' --password='''''wikidb_userpassword''''' '''''wikidb''''' > '''''file.sql'''''
 mysqldump --user='''''wikidb_user''''' --password='''''wikidb_userpassword''''' '''''wikidb''''' --xml > '''''file.xml'''''
:* Bei PostgreSQL ist für einen Datenbank-Dump der <code>pg_restore</code> Befehl zu verwenden:
 pg_dump --create -Fc '''''wikidb''''' > '''''file.db.dump'''''
:* Bei SQLite gibt es ein MediaWiki Skript um ein Backup zu erstellen:
 php '''''wikifolder'''''/maintenance/sqlite.php --backup-to '''''file'''''
* Bilder und andere Mediendateien (der Inhalt des <code>images</code> Verzeichnis, benutzerdefiniertes Logo /skins/common/images/wiki.png)
* Konfigurationsdateien, bspw <code>LocalSettings.php</code> und <code>.htaccess</code> (wenn vorhanden)
* MediaWikis Programmdateien, inklusive allen Benutzeroberflächen (Skins) und Erweiterungen (Extensions), besonders wenn Sie diese modifiziert haben.

<span id="Unpack_the_new_files"></span>
== Neue Dateien entpacken ==

<span id="Using_a_tarball_package"></span>
=== Verwendung eines Tarball-Paketes ===

Sie können die neuen Dateien via FTP oder Befehlszeile einfügen. Nutzen Sie die Befehlszeile, wenn Sie dazu Zugang haben! Die Befehlszeile zu verwenden ist viel schneller, als jede einzelne Datei der Tausenden via FTP hochzuladen.

{{Note|1=Sie sollten den entpackten tarball in ein neues und leeres Verzeichnis auf dem Server ablegen. Wenn Sie den tarball stattdessen direkt in die bestehende alte Version entpacken, sollten Sie die Anweisungen auf der Seite [[#Back up existing files and the database|Back up existing files and the database]] beachten. Andernfalls, falls Sie irgendwelche Anpassungen vorgenommen haben, werden diese so überschrieben, dass keine Möglichkeit mehr bleibt, diese wieder herzustellen. Wenn Sie dazu die neue Version direkt über die bestehende entpacken, können Dateien zurückbleiben, welche die neue Version beim Aktualisieren beeinflussen. Es ist daher empfehlenswert, die Dateien in einem neuen Verzeichnis zu entpacken und die Anpassungen im neuen Verzeichnis vorzunehmen (LocalSettings.php, Bildverzeichnis, Erweiterungen und andere Anpassungen wie eigene Skins).}}

<span id="FTP_or_graphical"></span>
==== FTP oder grafisch ====

Falls kein Kommandozeilen-Zugriff auf den Server möglich ist, kann das MediaWiki tarball Archiv lokal auf einen Computer heruntergladen und mittels [http://www.7-zip.org/download.html 7zip] entpackt werden.

Nachdem alle Dateien und Ordner lokal entpackt wurden, können sie mit einem beliebigen FTP Programm auf den Server hoch geladen werden.

<div lang="en" dir="ltr" class="mw-content-ltr">
==== cPanel File Manager ====
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">cPanel is a popular interface provided by many web hosts.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This method is efficient because the files are uncompressed on the server itself.</span>

* <span lang="en" dir="ltr" class="mw-content-ltr">Navigate to the directory that holds your wiki folder.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Upload the mediawiki-1.xx.x.tar.gz file.</span> <span lang="en" dir="ltr" class="mw-content-ltr">You may need to hit "Reload" to see it.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Extract the mediawiki-1.xx.x.tar.gz file.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Reload again.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Confirm that the mediawiki-1.xx.x folder is present.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Delete the tar.gz file.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">Copy all necessary skins, extensions, image folders, customizations, and the LocalSettings.php into the new folder.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(See below.)</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">When you are ready to run update.php, rename your old wiki folder and your new wiki folder.</span> <span lang="en" dir="ltr" class="mw-content-ltr">(e.g. "w" becomes "w1.34" and then "mediawiki1.35.0" becomes "w".)</span> <span lang="en" dir="ltr" class="mw-content-ltr">This step is easily reversible if you run into problems.</span>

<span id="Command_line"></span>
==== Kommandozeile ====
Unter Umständen kann es nötig sein, das Kommando als <code>sudo</code> auszuführen, falls der aktuelle Benutzer auf den wiki Installationsverzeichnissen keine vollständigen Schreibrechte haben sollte.
Beim enttarren (entpacken) eines tarball Pakets wird normalerweise ein neues Verzeichnis für die neue wiki Version erstellt. Danach müssen die die alten Konfigurationsdateien und das image Verzeichnis, in dem sich Bilder befinden, aus dem alten, vorherigen Installationsordner in den neuen kopiert werden:

<code class="mw-code mw-highlight plainlinks" style="display:block"><!--
-->{{#tag:span|cd|class=nb}} /path/to/your/new/installation/  
wget https://releases.wikimedia.org/mediawiki/{{MW stable branch number}}/mediawiki-{{MW stable release number}}.tar.gz
tar xvzf mediawiki-{{MW stable release number}}.tar.gz
rm mediawiki-{{MW stable release number}}.tar.gz
</code>

(Open)Solaris Benutzer sollten <kbd>gtar</kbd> benutzen, oder:

 $ gzip -dc mediawiki-{{MW stable release number}}.tar.gz | tar xf -

<span id="Other_files"></span>
===Andere Dateien===

Nach dem entpacken das tarball Archivs, sollten einige Dateien und Ordner aus dem alten Installationsverzeichnis in das neue kopiert oder verschoben werden:
* <code>LocalSettings.php</code> - enthält Ihre alten Konfigurationseinstellungen.
* Das <code>images</code> (oder <code>uploads</code> in älteren Versionen) Verzeichnis, das alle ins Wiki hochgeladenen Dateien enthält, es sei denn es wurde ein anderes Uploadverzeichnis ausgewählt. Die Zugriffsrechte (Permissions) und der Besitzer (Ownership) müssen geändert werden.  <code>find ./images -type d -exec chmod 755 {} \;</code> und <code>chgrp -R apache images</code> (beispielweise falls der web user "apache" ist).
<div class="mw-translate-fuzzy">
* Einige Erweiterungen im <code>extensions</code> Verzeichnis. Es sollten immer die aktuellen Erweiterungen installiert und verwendet werden, veraltete Erweiterungen funktionieren eventuell nicht korrekt oder gar nicht mit einer neueren MediaWiki-Version.
</div>
* Falls ein [[Special:MyLanguage/Manual:$wgLogo|benutzerdefiniertes Logo]] verwendet wird, muss diese Datei ebenfalls aus der Sicherungsdatei wiederherstellt werden. In Versionen vor 1.24 befindet es sich normalerweise im Verzeichnis <code>skins/common/images/</code>. Ab Version 1.24 im Verzeichnis <code>resources/assets/</code> oder <code>images/</code>, je nach dem welches zur Verwendung ausgewählt wurde. Danach dies in der LocalSettings.php hinzufügen, zum Beispiel <syntaxhighlight lang=php inline>$wgLogo = "$wgScriptPath/images/logo.png";</syntaxhighlight>
<div class="mw-translate-fuzzy">
* Bei 1.35 müssen die Logos ggf. aus [[$logo3|wgLogos]] wiederhergestellt werden. Dann ist beispielsweise folgendes zur LocalSettings.php hinzuzufügen: $logo4
</div>
* benutzerdefinierte Skins aus dem <code>skins</code>-Verzeichnis
* jede Veränderung, die in den alten Installationsdateien oder Erweiterungen durchgeführt wurde.
* jede .htaccess Datei (falls Apache verwendet wird und irgendwelche Regeln in der .htaccess eingetragen wurden).

Machen Sie diesen neuen Ordner zum veröffentlichten Ordner auf dem Webserver, oder benennen Sie das alte Installationsverzeichnis um und benennen Sie dann das neue um, um den alten Namen zu erhalten.
<span lang="en" dir="ltr" class="mw-content-ltr">Change ownership and group of everything so the web server has access to the files.</span>

<span id="Using_Git"></span>
=== Git verwenden ===

Wenn Sie {{ll|Download from Git|Git}} verwenden, exportieren Sie die Dateien an einen sauberen Speicherort und kopieren Sie dann die alten benutzerdefinierten Dateien wie im vorherigen Abschnitt beschrieben an den neuen Speicherort.

Sie müssen auch einige externe PHP-Bibliotheken mit Composer oder einer bereitgestellten Sammlung installieren, die für die Wikimedia Wiki-Farm gepflegt wird.
Weitere Details zur Installation und Aktualisierung externer Bibliotheken finden Sie in der [[Download_from_Git#Fetch_external_libraries|Git-Download-Dokumentation]].

<span id="Using_patch"></span>
=== Verwendung eines Patches ===
Eine kleine Patchdatei wird in der Regel für ein Minor-Versions-Upgrade zur Verfügung gestellt.
Sie müssen [[w:de:patch (Unix)|patch]] manuell herunterladen, um dies verwenden zu können.
Nach dem manuellen Download von der [https://releases.wikimedia.org/mediawiki/ Dumps-Seite] extrahieren Sie sie oder folgen Sie den Anweisungen mit wget unten.
Patches sind inkrementell, Sie können '''keine Version überspringen'''.

# <kbd>cd</kbd> in Ihr Hauptverzeichnis von MediaWiki (das mit LocalSettings.php).
# Laden Sie die Patchdatei herunter und entpacken Sie sie mit <kbd>gunzip</kbd>.
# Verwenden Sie <code>patch -p1 --dry-run</code>, um zu überprüfen, was geändert wird (''z.B.''', <code>patch -p1 --dry-run -i ''mediawiki-x.xx.x.patch''</code>).
# Wenn alles in Ordnung ist, führen Sie <kbd>patch</kbd> erneut ohne <code>--dry-run</code> aus.
# Überprüfen Sie Ihre Special:Version und Sie sollten die neue Versionsnummer sehen.

<span id="Files_remaining_that_may_cause_errors"></span>
===Verbliebene Dateien, die Fehler verursachen können===

Wenn die neue Version in eine altes, bestehendes Installationsverzeichnis entpackt wurde, können einige alte Dateien Probleme mit der neuen Version verursachen.

<span id="Upgrade_extensions"></span>
== Erweiterungen aktualisieren ==

Einige Erweiterungen wurden angepasst, um mit der neuen Version der MediaWiki-Software arbeiten zu können. Stellen Sie sicher, dass Sie die jeweils aktuelle Version verwenden. Eventuell müssen sie Updates für spezifische Erweiterungen manuell einspielen.

Verschiedene [[Special:MyLanguage/tarballs|Tarball-Pakete]] enthalten Untergruppen von Erweiterungen mit eigener Versionierung, die dabei helfen, die passende Version für das vorhandene MediaWiki-Kern-Release zu finden.

<div lang="en" dir="ltr" class="mw-content-ltr">
[[Special:ExtensionDistributor|Extension Distributor]] works well for most people who want a snapshot of extensions that will work with their supported versions of MediaWiki.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">If you want a lot of extensions then [[Special:MyLanguage/Download from Git|downloading from Git]] is probably best.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If you don't have Git but you want to upgrade a lot of extensions, you might consider using [[MwExtUpgrader|mwExtUpgrader]].</span>

<span id="Adapt_your_LocalSettings.php"></span>
== Ihre LocalSettings.php anpassen ==

<div lang="en" dir="ltr" class="mw-content-ltr">
If you use the same <code>LocalSettings.php</code> from the old version, you may need to adapt it to how new versions handle it:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Skin registration ===
</div>
{{MW 1.24|and after}}
<div lang="en" dir="ltr" class="mw-content-ltr">
Since MediaWiki 1.24, bundled skins like Vector, Monobook, Modern and CologneBlue are no longer part of MediaWiki core, and they need to be registered explicitly in <code>LocalSettings.php</code> to use them, otherwise MediaWiki will warn that you don't have installed skins.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This is what you need to add to <code>LocalSettings.php</code> when upgrading from versions older than 1.24 and want to have available one of those skins:
</div>

<syntaxhighlight lang="php">
wfLoadSkin( 'Vector' );
wfLoadSkin( 'MonoBook' );
wfLoadSkin( 'Modern' );
wfLoadSkin( 'CologneBlue' );
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
Other skins may still not be adapted to the new [[Special:MyLanguage/Manual:Extension registration|skin registration]] system, so refer to the documentation page about each skin to see how to register it properly in case of problems.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Extension registration ===
</div>
{{MW 1.25|and after}}
<div lang="en" dir="ltr" class="mw-content-ltr">
Since MediaWiki 1.25, extensions use a new [[Special:MyLanguage/Manual:Extension registration|extension registration]] system.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Previously your <code>LocalSettings.php</code> would include something like:
</div>

<syntaxhighlight lang="php">
require_once "$IP/extensions/Cite/Cite.php";
require_once "$IP/extensions/Gadgets/Gadgets.php";
require_once "$IP/extensions/ImageMap/ImageMap.php";
require_once "$IP/extensions/InputBox/InputBox.php";
require_once "$IP/extensions/Nuke/Nuke.php";
require_once "$IP/extensions/ParserFunctions/ParserFunctions.php";
require_once "$IP/extensions/Poem/Poem.php";
require_once "$IP/extensions/SyntaxHighlight_GeSHi/SyntaxHighlight_GeSHi.php";
require_once "$IP/extensions/WikiEditor/WikiEditor.php";
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
This can be converted to:
</div>

<syntaxhighlight lang="php">
wfLoadExtension( 'Cite' );
wfLoadExtension( 'Gadgets' );
wfLoadExtension( 'ImageMap' );
wfLoadExtension( 'InputBox' );
wfLoadExtension( 'Nuke' );
wfLoadExtension( 'ParserFunctions' );
wfLoadExtension( 'Poem' );
wfLoadExtension( 'SyntaxHighlight_GeSHi' );
wfLoadExtension( 'WikiEditor' );
</syntaxhighlight>

<span lang="en" dir="ltr" class="mw-content-ltr">Extensions are being adapted to use the new extension registration system.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Extensions that are not adapted should use the old way of installing them.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Refer to the installation instructions on the extension's page for more information.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Remove DefaultSettings.php line (if necessary) ===
</div> 
<span lang="en" dir="ltr" class="mw-content-ltr">Older versions of MediaWiki automatically generated a line in LocalSettings.php calling {{ll|Manual:DefaultSettings.php|DefaultSettings.php}}.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">As of Version 1.38, this line is deprecated and does not work with many extensions.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It needs to be removed.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Delete the following line:</span>
<syntaxhighlight lang="php">
require_once( "$IP/includes/DefaultSettings.php" );
</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Other variables ===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">Some variables may be obsolete or even removed.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Having them in <code>LocalSettings.php</code> '''usually''' won't have any effect.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">New variables may be added in newer versions, or some existing variables changed their type.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">We usually try to use sane defaults for them, and in case of type change, be backward compatible.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In any case, take a look at the release notes to see those changes.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Run the update script ==
</div>
<!--
NOTE TO EDITORS: As of r72451 <https://www.mediawiki.org/wiki/Special:Code/MediaWiki/72451>, this section name is linked from an error message hard-coded into MediaWiki, so if you change the section name, add <span id="Run_the_update_script"></span> or something so that the links still work.
-->
<div lang="en" dir="ltr" class="mw-content-ltr">
You can upgrade the MediaWiki database in two ways: Either from the command line or from the web browser. If you have shell access to your server, upgrading from the command line is recommended, since this reduces the risk of the upgrade process being interrupted by a timeout or connection reset.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The script will also notify you if any of MediaWiki core's PHP dependencies are out of date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Command line ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Access the command line of your server or an SSH shell or similar. You can access the command line by connecting to your server via SSH. If the local PC you are working on runs Microsoft Windows, you will need a tool like [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html PuTTY] to use SSH. From the command line or the Shell, execute the [[Special:MyLanguage/Manual:update.php|update script]]:
</div>

{{MW version|version=1.40|comment=and after}}
 $ php maintenance/run.php update.php

{{MW version|version=1.39|comment=and before}}
 $ php maintenance/update.php

<span lang="en" dir="ltr" class="mw-content-ltr">On a Linux server if you get an error, try performing the same command as root (by using the <kbd>sudo</kbd> command).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Note for simple installations on Windows (e.g. with {{ll|Manual:Installing MediaWiki on XAMPP|XAMPP}}):</span>
<span lang="en" dir="ltr" class="mw-content-ltr">First make sure that your web server (such as Apache) and your database (such as MySQL) are running.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Then run <code>update.php</code>: right-click it, select Open With, and browse to PHP.exe.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The resulting command prompt window will likely autoclose when the schema upgrade completes.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
MediaWiki will inspect the existing schema and update it to work with the new code, adding tables and columns as needed.
</div>

{{Note|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you use a [[Special:MyLanguage/Manual:Shared database|Shared database]], you should pass the <code>--doshared</code> parameter if you want the shared tables to be updated. Otherwise, they won't be touched by the update script.</span>}}

==== What to do if it says "MediaWiki requires PHP x.y.z or higher; you are using PHP x.w.v" ====

See [[Manual:Common errors and symptoms#MediaWiki requires PHP 7.4.3 or higher; you are using PHP 7.3.17]]

<div lang="en" dir="ltr" class="mw-content-ltr">
==== What to do if php update.php fails to do anything, resulting in a quick pause and then return to command prompt ====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
This can be caused by a malfunctioning extension or skin.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Check that all extensions and skins called for in LocalSettings.php are present
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Check that extensions are using the correct registration method (wfLoadExtension vs. require_once)
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Comment out the first half of the extensions in LocalSettings.php.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">If this causes update.php to work, uncomment half of that half (so 1/4 of the extensions).</span> <span lang="en" dir="ltr" class="mw-content-ltr">If this does NOT cause update.php to work, uncomment the first half but comment out the second half, and then comment out half of the second half, etc.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Repeat until update.php works to find the one that is failing.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
==== What to do in case of "ALTER command denied to user" error (or similar) ====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In case the scripts abort with a message similar to:
</div>

<pre>
Error: 1142 ALTER command denied to user 'wiki'@'localhost' for table 'mytable' (localhost)
ERROR: must be the owner of the mytable relation 
</pre>

<div lang="en" dir="ltr" class="mw-content-ltr">
This means that you should check that you have defined {{ll|Manual:$wgDBadminuser|$wgDBadminuser}} and {{ll|Manual:$wgDBadminpassword|$wgDBadminpassword}} in your {{ll|Manual:LocalSettings.php|LocalSettings.php}} file (in the main directory). These are the user and password needed by this script in order to access to the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, an old $wgDBmwschema variable (for Postgres) seems to be read for the table name to update instead of $wgDBname, even when MySQL is used.  If this is the case, just get rid of the $wgDBmwschema definition in LocalSettings.php.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====What to do in case of 'register_argc_argv is set to false' error====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may encounter the error:
</div>
<pre style="overflow:auto;">
Cannot get command line arguments, register_argc_argv is set to false
</pre>

<div lang="en" dir="ltr" class="mw-content-ltr">
# Go to ~/maintenance. Either edit an existing 'php.ini' file, or create one.
</div> 
<div lang="en" dir="ltr" class="mw-content-ltr">
# Add a line as follows:
</div>

<pre style="overflow:auto;">
register_argc_argv=true
</pre>

<div lang="en" dir="ltr" class="mw-content-ltr">
# Re-run <code>php update.php</code>
</div>

{{Anchor|Web_updater}}
<div lang="en" dir="ltr" class="mw-content-ltr">
===Web browser===
</div>
{{MW 1.17|and after}}
<div lang="en" dir="ltr" class="mw-content-ltr">
: ''See also {{ll|Manual:update.php|update.php}}''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is already big and in high production usage, then you should not be using the Web updater, e.g. because the update process will time out when the ''maximum_execution_time'' is reached. In that case you should use [[update.php]] from the command-line interface (not from the web). What exactly is "too big" depends on your server (e.g. on its performance, the load and on how long the maximum execution time of PHP allows the script to run). If your wiki is too big for the web updater and your hosting provider does not allow command-line access, then you need to migrate your wiki to another hosting account, preferably to one that does have shell access.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
# Always [[Special:MyLanguage/Manual:Backing up a wiki|back up]] before performing database maintenance.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Navigate your web browser to <code>'''/mw-config/index.php'''</code>.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">For example, if your wiki is at <code><nowiki>http://example.org/w/index.php</nowiki></code>, then navigate to <code><nowiki>http://example.org/w/mw-config/index.php</nowiki></code>.</span>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Select your language and click continue.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# The existing installation should be detected. Follow the instructions on the screen to upgrade it.<br/>If asked for the "upgrade key", open your {{ll|Manual:LocalSettings.php|LocalSettings.php}} file and look for the key assigned to {{ll|Manual:$wgUpgradeKey|$wgUpgradeKey}}.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It might happen that the web-updater does not seem to work: Instead of seeing the initial language selection screen, you might see an empty wiki page, possibly with some error message. In this case it is most likely that your web server uses Rewrite Rules (most likely for [[Special:MyLanguage/Manual:Short URL|short URLs]]), which do not show you the updater at ''mw-config/'', but a wiki page at ''Mw-config/'', with capital "M". In this case, rename the ''.htaccess'' file for the time of the update. Then you should be able to access the web-updater.
</div>

{{Warning|1=<span lang="en" dir="ltr" class="mw-content-ltr">If you use this method, make sure to '''change the name of the .htaccess file back''' after running the upgrade script! Otherwise, short URLs and possibly other stuff will be broken!</span>}}


<div lang="en" dir="ltr" class="mw-content-ltr">
== Test the update ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the upgrade has been completed, browse to the wiki and check that the following operations work as expected:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Viewing pages
* Editing pages
* Uploading a file
* Visit [[Special:Version]] and check that the version shown is correct and that the extensions are present.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Remove leftovers from old installations ==
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">If you have copied your previous installation to another folder on the server, be sure to remove it or make it completely inaccessible from the web.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">It is very important to not leave old installations accessible from the web, since it completely defeats the purpose of upgrading, and leaves your server open to attacks.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Frequently asked questions ==
</div>
<section begin=FAQ />
<div lang="en" dir="ltr" class="mw-content-ltr">
===How hard is it to upgrade?===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the only file you have modified is {{ll|Manual:LocalSettings.php|LocalSettings.php}}, and you are upgrading from 1.5 or later, the process is very simple. The amount of human work involved is only a few minutes. The database schema changes will take an amount of time proportional to the size of your database — potentially hours for wikis with millions of pages, but for a more typical size of a few thousand pages, it is usually done in seconds.
</div>

<span lang="en" dir="ltr" class="mw-content-ltr">Minor upgrades, within the same major version, say from {{MW legacy branch number}}.0 to {{MW legacy release number}}, do not require any schema changes at all.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You can just update the files. The database needs no update, hence it is not necessary to run the updater script.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Upgrading from 1.4 or earlier is potentially complicated because support for character sets other than UTF-8 was dropped, and the schema for storing bulk text changed. Please read the relevant section in the <code>UPGRADE</code> file.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Upgrading becomes difficult if you have modified our source code, and you don't want your changes to be overwritten. Tools such as [http://www.gnu.org/software/diffutils/diffutils.html diff], [http://www.gnu.org/software/patch/ patch], [http://meldmerge.org/ Meld] or [http://winmerge.org/ WinMerge] may be useful. There is also potential for trouble if you are using unmaintained extensions. Upgrade your extensions at the same time as you upgrade MediaWiki.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have modified the skin or use a custom skin, you very likely will have to adjust it to work again with the new version of MediaWiki.
</div>

{{Tip|1=<span lang="en" dir="ltr" class="mw-content-ltr">Instead of patching your "global" CSS and JS (JavaScript) files every time, you can simply add the code to your MediaWiki:Common.js and MediaWiki:Common.css pages. As these are part of the database which will be reused when you upgrade, you will not have to patch the MediaWiki core files any more.</span>}}

<div lang="en" dir="ltr" class="mw-content-ltr">
===How do I upgrade from a really old version? In one step, or in several steps?===
</div>
{{MW 1.4|and before}}
<span lang="en" dir="ltr" class="mw-content-ltr">It depends: If you are '''upgrading from MediaWiki 1.4 or older''', you should upgrade to MediaWiki 1.5 first.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If you are upgrading from a Latin-1 wiki, use upgrade1_5.php (found in MediaWiki 1.5) to convert the relevant parts of the database to UTF-8 ({{ll|Manual:$wgUseLatin1|$wgUseLatin1}} needs to be set to true in your {{ll|Manual:LocalSettings.php|LocalSettings.php}} for this to work).</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Next, run update.php, and then set the {{ll|Manual:$wgLegacyEncoding|$wgLegacyEncoding}} option in LocalSettings.php to the encoding previously used by the wiki (e.g. windows-1252). This is basically how Wikipedia and other Wikimedia Foundation sites were upgraded from MediaWiki 1.4 to 1.5 – see some [[wikitech:Obsolete:1.5 upgrade|related notes at Wikitech]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You may need to upgrade to MediaWiki 1.4 before running the upgrade1.5 script.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If you want to make a database dump (e.g. MySQL) of your Latin-1 wiki, make sure the type of the <code>old_text</code> field in the {{ll|Manual:Text table|text}} table is <code>mediumblob</code>, not <code>mediumtext</code>, to avoid character encoding issues.</span>
{{MW version|version=1.5|version2=1.35}}
<span lang="en" dir="ltr" class="mw-content-ltr">If you are '''upgrading from MediaWiki 1.5 or newer''' to '''1.35''', you can upgrade in one step, from your old version to the latest stable version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">The vast majority of reports, as well as automated testing, indicate that doing it in one step works just fine.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">If you have trouble believing this, read [[mailarchive:mediawiki-l/2008-October/028975.html|this mailing list post]].</span>
<span lang="en" dir="ltr" class="mw-content-ltr">However, please note that when you update from old versions, chances that you will encounter PHP errors are bigger than when you upgrade from the version directly previous to the new version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">You would have received these errors anyway, had you not skipped versions, but the errors would have been associated with each individual update.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Instead, if you update several versions at once, you'll get the same set of errors all at the same time.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">This will make the upgrade more difficult, but do not forget that you did not have the trouble of updating to the intermediate versions, which you skipped!</span>
{{MW 1.35|and after}}
<div lang="en" dir="ltr" class="mw-content-ltr">
If you are '''upgrading to MediaWiki 1.36''' or later, only upgrades from the last two LTS releases will be supported ([[phab:T259771]]). This will mean that for very old versions, that you first upgrade to MediaWiki 1.35 and then upgrade to 1.36.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Should I back up first?===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Short answer: Yes.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Long answer: It depends on a) how much you value your data, b) how hard it is to create a backup and c) how confident you are with MySQL maintenance and administration.
</div> 

<span lang="en" dir="ltr" class="mw-content-ltr">An upgrade failure may leave your database in an inconsistent state, in between two versions.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">A PHP or MySQL error might happen during upgrade leaving your database partly upgraded.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">In such situations it may be possible to somehow fix this problem with much manual work.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">However, it will be ''way easier'' to just put a database backup from before running update.php in place and to continue with that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Otherwise you might have hours of - needless - work.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">Recovery is often complex.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Volunteers on the support forums are unlikely to be impressed if you neglect to make a backup and then need help to recover from upgrade-related corruption.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">A better outcome is if you can revert to your backup, and then [[phab:maniphest/task/create/|report the bug against the corresponding MediaWiki project]] in the upgrade process which caused the corruption.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Can I keep my LocalSettings.php?===
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">Yes, but you may have to make some minor changes. The format of {{ll|Manual:LocalSettings.php|LocalSettings.php}} is largely backward compatible.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">Changes which break LocalSettings.php compatibility will be documented in the "configuration changes" section of the [[Special:MyLanguage/Release notes|release notes]].</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Can my wiki stay online while it is upgrading?===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Generally yes, however if you upgrade via Git, Git may temporarily (for a few seconds) break it.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you are upgrading between minor releases of MediaWiki, all you need to do is update the source files.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Note: the following assumes you have command line access. If you are upgrading between major releases of MediaWiki, the preferred procedure is as follows:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
# Unpack the new version of MediaWiki into a new directory
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Prepare that new directory: copy your current LocalSettings.php from the old directory, copy any installed extensions and custom skins (if any). Check {{wg|Logo}} and {{wg|Logos}} settings in LocalSettings.php and if necessary copy logo file from the old directory to the new directory.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# In the release notes for the new version, see if any changes need to be made to LocalSettings.php.
</div>
# <span lang="en" dir="ltr" class="mw-content-ltr">In the old directory, edit LocalSettings.php and insert the following code.</span> <span lang="en" dir="ltr" class="mw-content-ltr">This will place the database in read-only mode for regular wiki activity, without restricting your own update actions.</span> <span lang="en" dir="ltr" class="mw-content-ltr">Users will see the message provided if they attempt an edit during the upgrade process:</span><br /><div class="mw-highlight mw-highlight-lang-php"><div class="mw-code">$adminTask = ( {{#tag:span|PHP_SAPI|class=no}} === {{#tag:span|'cli'|class=s1}} || {{#tag:span|defined|class=nb}}( {{#tag:span|'MEDIAWIKI_INSTALL'|class=s1}} ) );<br />{{ll|Manual:$wgReadOnly|$wgReadOnly}} = $adminTask ? {{#tag:span|false|class=k}} : {{#tag:span|'Upgrading to MediaWiki {{MW stable release number}}'|class=s1}};</div></div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Run the [[Special:MyLanguage/Manual:Upgrading#Command_line|update script]] or the web updater in the new directory.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Copy the images from the images sub-directory from the old directory to the new directory.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Swap the old directory and the new directory.
</div> <span lang="en" dir="ltr" class="mw-content-ltr">(This will make the database writable again, because {{ll|Manual:$wgReadOnly|$wgReadOnly}} was only set in the old directory's LocalSettings.php.)</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Why upgrade?===
</div>
:''<span lang="en" dir="ltr" class="mw-content-ltr">Subscribe to [[mail:mediawiki-announce|mediawiki-announce]] to be notified of new releases.</span>''

<div lang="en" dir="ltr" class="mw-content-ltr">
Recent releases receive security fixes to keep your wiki and your host safe from vandals, while old releases don't (see {{ll|Version lifecycle}}).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
New major releases come with new features, which you might want to use: see the [[Special:MyLanguage/Release notes|release notes]] for details.
</div>
<section end=FAQ />

<div lang="en" dir="ltr" class="mw-content-ltr">
== See also ==
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Greg Sabino Mullane's Blog post provides some [https://www.endpointdev.com/blog/2014/10/mediawiki-minor-upgrade-with-patches/ more detail about point release upgrades].
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[Special:MyLanguage/Communication|Help and Support]] if you need help or something went wrong
</div>
* {{ll|Category:MediaWiki deprecated or obsolete features}}
* {{ll|Manual:Backing up a wiki}}
* {{ll|Manual:Restoring a wiki from backup}}
* {{ll|Manual:Moving a wiki}}
* {{ll|Manual:Restoring wiki code from cached HTML}} - <span lang="en" dir="ltr" class="mw-content-ltr">if you don't have a successful backup</span>
* {{ll|Manual:Installing MediaWiki}}

[[Category:MediaWiki administration{{#translation:}}|{{PAGENAME}}]]
[[Category:MediaWiki for site admins{{#translation:}}]]
[[Category:MediaWiki development{{#translation:}}|Upgrading to *]]
[[Category:Upgrading{{#translation:}}|Upgrading to *]]