Manual:Upgrading/hy

Ֆայլի փոխանցումը
Ընտրե՛ք ֆայլերի փոխանցման մեթոդ.


 * wget
 * Ապահով պատեճենե՛ք օգտագործելով SCP կամ WinSCP
 * SSH File Transfer Protocol (SFTP)
 * FTP հաճախորդ (կլիենտ) ծրագրի օգտագործումը
 * Հոսթինգ ծառայություն տրամադրող ընկերությունը կարող է վեբ բրաուզերի միջոցով տրամադրել ֆայլերի կառավարման միջերես (ինտերֆեյս), որի առկայությունը կարող եք ճշտեք ձեր ինտերնետ մատակարարի հետ:
 * Մեկ այլ մեթոդ Դրանց ցուցակն առկա է List of file transfer protocols

Նախնական
Կարդեցե՛ք.


 * 1) Ստուգե՛ք պահանջները
 * 2) Կարդացե՛ք RELEASE-NOTES ֆայլը
 * 3) Read the UPGRADE file
 * 4) Պահուստավորե՛ք առկա ֆայլերը և տվյալների շտեմարանը
 * 5) Ապափաթեթավորե՛ք նոր ֆայլերը
 * 6) Արդիականացրե՛ք ընդլայնումները
 * 7) Գործարկե՛ք թարմացման սկրիպտը՝ ստուգելու համար տվյալների շտեմարանը
 * 8) Ստուգե՛ք թարմացումը
 * 9) Հեռացրե՛ք հին տեղադրումներից մնացած ֆայլերը

Ստուգե՛ք պահանջները
MediaWiki պահանջում է՝


 * PHP +
 * Հետևյալներից մեկը․
 * MariaDB +
 * MySQL +
 * PostgreSQL +
 * SQLite +

Սկսած 1.36 տարբերակից MediaWiki-ն հանձնառու է աջակցել արդիականացումները միայն նախորդող երկու LTS թողարկումներից (տե՛ս T259771): MediaWiki-ի ավելի հին տարբերակներից արդիականացումները պետք է իրականացվեն մի քանի քայլով: Սա նշանակում է, որ եթե դուք ցանկանում եք արդիականացնել 1․23-ից կամ ավելի վաղ ստեղծված թողարկումից մինչև 1․36, ապա առաջինը դուք պետք է արդիականացնեք 1․23 wiki-ն մինչև 1․27 (կամ 1.35), իսկ դրանից հետո 1.27-ից (կամ 1.35-ից) դուք կարող եք արդիականացնել մինչև 1․36 թողարկումը։

Եթե դուք օգտագործում եք PostgreSQL, խնդրում ենք կարդացեք նաև ։

Լրացուցիչ տեղեկատվության համար խնդրում ենք կարդալ և ։

Կարդացե՛ք թողարկման ծանոթագրությունները
Բաշխման ֆայլի կամ Git-ից ստացված/ներմուծված ֆայլերի մեջ կան մի շարք ֆայլեր՝ մեծատառ անվանումներով, որոնցից մեկը պարունակում է  (wiki)-ը։ Այժմ ժամանակն է բացելու այն և պարզելու թե ի՞նչ է փոխվել այս թողարկման մեջ։ Դուք նաև պետք է կարդաք UPGRADE ֆայլի հրահանգները։

Մաքրել սպասման մեջ գտնվող առաջադրանքները
Կատարողականության տեսանկյունից որոշ գործողություններ տվյալների պահոցում հետաձգվում են և կառավարվում job queue-ի կողմից։ Այս առաջադրանքները պահպանվում են տվյալների պահոցում և պարունակում են պարամետրեր կատարման ենթակա գործողությունների վերաբերյալ տեղեկատվության հետ միասին։ Հաստատակամորեն խորհուրդ է տրվում գործարկել այդ սպասման մեջ գտնվող առաջադրանքները մինչև wiki-ի արդիականացումը՝ խուսափելու համար ձախողումից այն դեպքում, երբ այդ առաջադրանքների պարամետրական բնորոշումը փոխվում է նոր թողարկման մեջ։ Օգտագործե՛ք գործարկելու բոլոր սպասման մեջ գտնվող առաջադրանքները և մաքրելու առաջադրանքների հերթը մինչև արդիականացման կատարումը։

Պահուստավորե՛ք գոյություն ունեցող ֆայլերը և տվյալների պահոցը
Ամբողջական հրահանգներ․ 

Թեև արդիականացման սկրիպտները լավ մշակված են և հուսալի՝ ամեն ինչ կարող է գնալ ոչ այնպես, ինչպես ցանկալի է։ Մինչև տվյալների պահոցի սխեմայի թարմացման գործարկումը wiki-ի կատարեք ամբողջական պահուստավորում՝


 * wiki-ի բովանդակությունը տվյալների պահոցից, (համոզվեք որ ճիշտ եք նշել սիմվոլների հավաքածուն, առաջինը ստուգե՛ք LocalSettings.php-ն)։ Լավ կլինի տվյալների պահոցի SQL dump-ի հետ ստեղծել նաև XML dump-ը։
 * MySQL, թե՛ SQL dump-ը և թե՛ XML dump-ը օգտագործվում են  հրամանի հետ․

mysqldump --user=wikidb_user --password=wikidb_userpassword wikidb > file.sql mysqldump --user=wikidb_user --password=wikidb_userpassword wikidb --xml > file.xml
 * PostgreSQL, տվյալների պահոցի dump-ը օգտագործվում է  հրամանի հետ․

pg_dump --create -Fc wikidb > file.db.dump
 * SQLite, դուք օգտագործում եք MediaWiki-ի սկրիպտը պահուստ ստեղծելու համար՝

php wikifolder/maintenance/sqlite.php --backup-to file
 * պատկերները և այլ մեդիա ֆայլերը ( պանակի պարունակությունը՝ logo /skins/common/images/wiki.png)
 * կոնֆիգուրացիան ֆայլեր, օրինակ՝  և   (եթե առկա է)
 * MediaWiki-ի ծրագրային ֆայլերը, ներառյալ բոլոր տեսքերը և ընդլայնումները, հատկապես եթե դուք ձևափոխել եք դրանք։

Tarball փաթեթի օգտագործումը
Դուք կարող եք տեղադրել նոր ֆայլը անհրաժեշտ տեղում՝ օգտագործելով FTP կամ հրամանների տող։ Օգտագործե՛ք հրամանների տողը, եթե դուք ունեք հասանելիություն դրան։ Հրամանի տողի օգտագործումը շատ ավելի արագ կլինի, քան հազարավոր ֆայլերից յուրաքանչյուրը FTP-ի միջոցով վերբեռնելը:

FTP կամ գրաֆիկական
Եթե դուք հասանելի չեք ձեր սերվերի հրամանների տողին, ներբեռնեք MediaWiki-ի tarball-ը ձեր տեղային համակարգչի մեջ և օգտագործեք 7zip-ը ձեր տեղային PC-ի մեջ tarball-ը ապաարխիվացնելու համար։

After you extracted the files locally, use your favorite FTP client software to upload directories and files to the server.

cPanel File Manager
cPanel is a popular interface provided by many web hosts. This method is efficient because the files are uncompressed on the server itself.


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

Command line
You may need to run the command as  if you don't have full write permissions to the wiki install directories under your current user. When untarring a tarball package normally a new directory for the new wiki version will be created and you will have to copy the old configuration files and images directory from your old installation directory:

(Open)Solaris users should use gtar, or:

$ gzip -dc mediawiki-.tar.gz | tar xf -

Other files
After extracting the tarball, you should copy or move some files and folders from the old installation directory to the new one:
 * - contains your old configuration settings.
 * The  (or   in older versions) directory, which contains all the uploaded files to the wiki, unless you have chosen a different upload directory, and change the ownership and permissions.   and   (e.g. if your web user is apache).
 * Some extensions in the  directory. You should always get updated extensions; old extensions aren't guaranteed to work with a newer version of MediaWiki.
 * In case you use a custom logo this file also needs to be restored from backup. Before 1.24 the logo is usually in . After 1.24 the logo is usually in   or   if that's what you chose to use. Then add to LocalSettings.php e.g.
 * For 1.35 you may need to restore the logos from . Then add to LocalSettings.php e.g.
 * Custom skins from within the  directory.
 * Any modifications made to the old installation files or extensions.
 * Any .htaccess file (if you're using Apache and you've defined any rules in them).

Once done, make this new folder the published folder on the web server, or rename the old installation directory and then rename the new one to match the old name.

Using Git
If using, export the files into a clean location, and then copy the old customized files into the new location as described in the previous section.

You will also need to install some external PHP libraries using Composer or a provided collection maintained for the Wikimedia wiki farm. More details on installing and updating external libraries can be found in the Git download documentation.

Using patch
A small patch file is usually made available for a minor version upgrade. You'll need to download patch to use this. Manually download and extract the patch file from the dumps site or follow the directions with wget below. Patches are incremental, you can not  skip a version.


 * 1) cd to your main MediaWiki directory (the one with LocalSettings.php).
 * 1) Download the patch file and gunzip it.
 * 1) Use   to check what will be changed (e.g.,  )
 * 1) If all is well, run patch again without.
 * 1) Check your Special:Version and you should see the new version number in place.

Files remaining that may cause errors
If you unpacked over the old installation directory, some old files can cause problems with the new version.

If you are not using profiling, but have a  file in the MediaWiki root folder, you may receive errors referring to. Deleting, or renaming, the  file will resolve this error. The  file, also in the MediaWiki root folder, can serve as a template should you enable profiling in the future.

MediaWiki 1.23 deprecates the skin autodiscovery mechanism of core skin files. After upgrading to this version, you should ensure that the old files,  ,   and   directly in the   directory as well as the according subfolders inside the   directory got removed. MediaWiki will log warnings if any of them are still found to help you remember. (You will also need to adjust any custom skins to follow a similar convention.) See for details.

MediaWiki 1.24 changes the paths of core skin files. After upgrading to this version, you should ensure that the old files,  ,   and   directly in the   directory are no longer present. See for details.

Upgrade extensions
Certain extensions have been updated in order to work with the new version of MediaWiki. Be sure to upgrade to the latest versions of such extensions. You might need to perform manual updates to custom extensions.

Different tarballs include some subsets of extensions and have versioning which helps you upgrade choosing the right one for your MediaWiki core release.

Extension Distributor works well for most people who want a snapshot of extensions that will work with their supported versions of MediaWiki.

If you want a lot of extensions then downloading from Git is probably best. If you don't have Git but you want to upgrade a lot of extensions, you might consider using mwExtUpgrader.

Adapt your LocalSettings.php
If you use the same  from the old version, you may need to adapt it to how new versions handle it:

Skin registration
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  to use them, otherwise MediaWiki will warn that you don't have installed skins.

This is what you need to add to  when upgrading from versions older than 1.24 and want to have available one of those skins:

Other skins may still not be adapted to the new skin registration system, so refer to the documentation page about each skin to see how to register it properly in case of problems.

Extension registration
Since MediaWiki 1.25, extensions use a new extension registration system.

Previously your  would include something like:

This can be converted to:

Extensions are being adapted to use the new extension registration system. Extensions that are not adapted should use the old way of installing them. Refer to the installation instructions on the extension's page for more information.

Other variables
Some variables may be obsolete or even removed. Having them in  usually won't have any effect. New variables may be added in newer versions, or some existing variables changed their type. We usually try to use sane defaults for them, and in case of type change, be backward compatible. In any case, take a look at the release notes to see those changes.

Run the update script
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.

The script will also attempt to download any missing dependencies which MediaWiki needs.

Command line
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 PuTTY to use SSH. From the command line or the Shell, change to the  directory and execute the update script:

$ php update.php

On a Linux server if you get an error, try performing the same command as root ( sudo php update.php ). Note for simple installations on Windows (e.g. with ): First make sure that your web server (such as Apache) and your database (such as MySQL) are running. Then run : right-click it, select Open With, and browse to PHP.exe. The resulting command prompt window will likely autoclose when the schema upgrade completes.

You might see a message that your PHP version is too old and that MediaWiki needs a newer version. After that message, the update aborts. Reason for this error is that the command line can use another PHP version than that one which you have when you execute MediaWiki from the web server. When you get this message you should check, if you can execute a newer PHP version on the shell by using a different command: That might e.g. be php5 or php56. If another version is available and - if so - under which name, depends on the setup of your server. If it does not work, ask your hoster; they will surely know.

MediaWiki will inspect the existing schema and update it to work with the new code, adding tables and columns as needed.

What to do if php update.php fails to do anything, resulting in a quick pause and then return to command prompt
This can be caused by a malfunctioning extension or skin.

If this causes update.php to work, uncomment half of that half (so 1/4 of the extensions). 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. Repeat until update.php works to find the one that is failing.
 * Check that all extensions and skins called for in LocalSettings.php are present
 * Check that extensions are using the correct registration method (wfLoadExtension vs. require_once)
 * Comment out the first half of the extensions in LocalSettings.php.

What to do in case of "ALTER command denied to user" error (or similar)
In case the scripts abort with a message similar to:

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

This means that you should check that you have defined and  in your  file (in the main directory). These are the user and password needed by this script in order to access to the database.

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.

What to do in case of "unexpected T_STRING" error
Individuals running update.php from the command line may encounter the following error:

 syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' \ in ~/maintenance/commandLine.inc on line 13

This error occurs when update.php is run from php4.

Individuals who have their site hosted by providers who provide both php4 and php5 should take the following steps:


 * 1) from the command line, enter the command 'whereis php5'
 * 1) once you have discerned the location of the php5 path, list the contents of php5/bin directory
 * 1) once you've determined the name of the PHP executable (either PHP or php5), type in the entire path to execute update.php

Below is an example:

 $ command -v php5 $ ls -la /usr/local/php5/bin $ /usr/local/php5/bin/php update.php

What to do in case of 'register_argc_argv is set to false' error
You may encounter the error:  Cannot get command line arguments, register_argc_argv is set to false


 * 1) Go to ~/maintenance. Either edit an existing 'php.ini' file, or create one.
 * 1) Add a line as follows:

 register_argc_argv=true


 * 1) Re-run

Web browser

 * See also 

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.

For example, if your wiki is at, then navigate to.
 * 1) Always back up before performing database maintenance.
 * 1) Navigate your web browser to.
 * 1) Select your language and click continue.
 * 1) The existing installation should be detected. Follow the instructions on the screen to upgrade it. If asked for the "upgrade key", open your  file and look for the key assigned to.

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

Test the update
Once the upgrade has been completed, browse to the wiki and check that the following operations work as expected:


 * Viewing pages
 * Editing pages
 * Uploading a file
 * Visit Special:Version and check that the version shown is correct and that the extensions are present.

Remove leftovers from old installations
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. 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.

Frequently asked questions


How hard is it to upgrade?
If the only file you have modified is, 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.

Minor upgrades, within the same major version, say from .0 to, do not require any schema changes at all. You can just update the files. The database needs no update, hence it is not necessary to run the updater script.

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

Upgrading becomes difficult if you have modified our source code, and you don't want your changes to be overwritten. Tools such as diff, patch, Meld or 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.

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.

How do I upgrade from a really old version? In one step, or in several steps?
It depends: If you are upgrading from MediaWiki 1.4 or older, you should upgrade to MediaWiki 1.5 first. 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 ( needs to be set to true in your for this to work). Next, run update.php, and then set the 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 the settings page for enwiki and some related notes at Wikitech. You may need to upgrade to MediaWiki 1.4 before running the upgrade1.5 script. If you want to make a database dump (e.g. MySQL) of your Latin-1 wiki, make sure the type of the  field in the  table is , not  , to avoid character encoding issues.

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. The vast majority of reports, as well as automated testing, indicate that doing it in one step works just fine. If you have trouble believing this, read this mailing list post. 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. You would have received these errors anyway, had you not skipped versions, but the errors would have been associated with each individual update. Instead, if you update several versions at once, you'll get the same set of errors all at the same time. 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!

If you are upgrading to MediaWiki 1.36 or later, only upgrades from the last two LTS releases will be supported (T259771). This will mean that for very old versions, that you first upgrade to MediaWiki 1.35 and then upgrade to 1.36.

Should I back up first?
Short answer: Yes.

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.

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

Recovery is often complex. 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. A better outcome is if you can revert to your backup, and then report the bug against the corresponding MediaWiki project in the upgrade process which caused the corruption.

Can I keep my LocalSettings.php?
Yes, but you may have to make some minor changes. The format of is largely backward compatible. Changes which break LocalSettings.php compatibility will be documented in the "configuration changes" section of the release notes.

Can my wiki stay online while it is upgrading?
Generally yes, however Git may temporarily (for a few seconds) break it.

If you are upgrading between minor releases of MediaWiki, all you need to do is update the source files.

Note: the following assumes you have command line access. If you are upgrading between major releases of MediaWiki, the preferred procedure is as follows:


 * 1) Unpack the new version of MediaWiki into a new directory
 * 1) Prepare that new directory: copy your current LocalSettings.php from the old directory, copy any installed extensions and custom skins (if any). Check  and  settings in LocalSettings.php and if necessary copy logo file from the old directory to the new directory.
 * 1) In the release notes for the new version, see if any changes need to be made to LocalSettings.php.
 * 1) Place the database in read-only mode by inserting the following variable into LocalSettings.php in the old directory - users will see this message if they attempt an edit during the upgrade process:


 * 1) * This no longer works since MediaWiki 1.27, which also prevents running the update script. A workaround for versions since MediaWiki 1.27 can be found in . See also.
 * 1) Run the update script or the web updater in the new directory.
 * 1) Copy the images from the images sub-directory from the old directory to the new directory.
 * 1) Swap the old directory and the new directory.

Why upgrade?

 *  Subscribe to mediawiki-announce to be notified of new releases. 

Because it's usually easy enough, a single step from your version to latest and also via web.

Recent releases receive security fixes to keep your wiki and your host safe from vandals, while old releases don't (see ). That makes dozens good reasons to upgrade!

New major releases come with new features, which you might want to use: see the release notes for details. In case you need additional arguments to convince your bosses to let you upgrade from a pretty old version, here is a summary:

InstantCommons no longer requires local files. Allow to block range of IPs. Added ability to search for contributions within an IP ranges at Special:Contributions. The was introduced. Add default edit rate limit of 90 edits/minute for all users. The "watch" feature can be enhanced with expiry dates.
 * Since, edits can be previewed before saving also as diff.
 * Since, an undo button is available.
 * Since, patrolling on Special:NewPages is much easier.
 * Since, you can rename (move) files.
 * Since, you can fix double redirects automatically.
 * Since, is available.
 * If you have appropriate caching, since 1.17 optimizes pageload speeds a lot.
 * Since 1.17, category sorting makes sense! (especially for non-English letters); extended to 68 languages after.
 * Since and, users of all languages and genders are correctly addressed by the interface and logs (before 1.15, no gender at all).
 * In the skinning system was reworked, making it easier to reuse parts of existing skins in your own skins.
 * Since 1.20, diffs are more readable.
 * In 1.21 and 1.23, email notifications become clearer and more predictable, making your wiki more effective.
 * Since 1.22, vandal fighting (patrolling) is less time-consuming.
 * In 1.24, password storage was improved to allow for better security.
 * Since 1.25, enhanced recent changes are available
 * In 1.26, the "ResourceLoader" mechanism was improved
 * In 1.27, the session management was reworked as well as the user authentication management completely modernized.
 * Since, the cache for rendered HTML of article pages improved.
 * Since, the Action API was reworked and improved. Also, user group assignments may now be done for a selectable period.
 * Since, the blocked users cannot change their email.
 * Since, some extensions are now part of the core, like , ,.
 * Since, MediaWiki supports over 350 languages.
 * Since, MediaWiki supports "partial blocks", where IPs and accounts can be restricted from editing particular pages or namespaces.
 * Since, more extensions part of the core: (for Lua modules), ,.
 * Since (a stable long-term support release),  is part of the core.

Also, in we started bundling some vital extensions, like a better editor and anti-vandalism tools ConfirmEdit and Nuke; more have been added in later releases. 