Manual:Upgrading/id



Transfer berkas
Pilih metode untuk mentransfer berkas:


 * wget
 * Penyalinan aman dengan SCP atau WinSCP
 * SSH File Transfer Protocol (SFTP)
 * Menggunakan sebuah klien FTP.
 * Perusahaan hosting mungkin menyediakan antrarmuka manajer berkas via peramban web; periksa penyedia Anda.
 * Suatu metode lain. Ada daftarnya di List of file transfer protocols

Persiapan
Bacalah.


 * 1) Periksa persyaratannya
 * 2) Baca catatan rilisnya
 * 3) Cadangkan berkas dan basis data yang sudah ada
 * 4) Ekstrak berkas-berkas baru
 * 5) Mutakhirkan ekstensi-ekstensinya
 * 6) Jalankan skrip pembaruan untuk memeriksa basis data
 * 7) Uji coba hasil pemutakhirannya
 * 8) Hapus sisa-sisa dari instalasi yang lama

Cek persyaratan
MediaWiki memerlukan:


 * PHP +
 * Salah satu di antara yang berikut:
 * MySQL + (atau ekuivalennya MariaDB)
 * PostgreSQL +
 * SQLite +

Jika Anda menggunakan PostgreSQL, tolong baca juga.

Untuk informasi lebih lanjut, tolong baca dan.

Baca catatan rilis
Di dalam tarball distribusi, atau di dalam berkas-berkas yang diperiksa/diekspor dari Git, terdapat beberapa berkas dengan nama berkas yang dikapitalkan, salah satunya berisi  (wiki). Sekarang waktunya membukanya dan mengetahui apa yang telah diubah dalam rilis ini.

Tuntaskan pekerjaan tertunda
Untuk alasan performa, beberapa tindakan dalam basis data ditunda, dan dikelola oleh antrean pekerjaan. Pekerjaan-pekerjaan disimpan dalam basis data dan berisi parameter-parameter dengan informasi mengenai tindakan yang dilakukannya. Sangat disarankan untuk menjalankan pekerjaan-pekerjaan yang ditunda sebelum memutakhirkan wiki, agar tidak terjadi masalah yang disebabkan spesifikasi parameter pekerjaan tersebut berubah di versi yang baru. Gunakan untuk menjalankan semua pekerjaan yang ditunda dan membersihkan antrean sebelum menjalankan pemutakhiran.

Cadangkan berkas dan basisdata yang sudah ada

 * Instruksi selengkapnya: 

Meskipun skrip pemutakhiran telah diperlihara dengan baik, masalah masih bisa terjadi. Sebelum memulai memutakhirkan skema basis data, buatlah cadangan lengkap wiki, termasuk seluruh basis data dan berkas:


 * konten wiki, dari basis data, (pastikan Anda menentukan set karakternya dengan benar, periksa dulu LocalSettings.php). Sebaiknya dibuat juga sebuah dump XML sebagai pelengkap dump basis data SQL.
 * MySQL, baik dump SQL dan dump XML digunakan dengan perintah :

mysqldump --user=wikidb_user --password=wikidb_userpassword wikidb > file.sql mysqldump --user=wikidb_user --password=wikidb_userpassword wikidb --xml > file.xml
 * PostgreSQL, dump basis data digunakan dengan perintah :

pg_dump --create -Fc wikidb > file.db.dump
 * SQLite, Anda menggunakan sebuah skrip MediaWiki untuk membuat salinan:

php wikifolder/maintenance/sqlite.php --backup-to file
 * gambar dan berkas media lainnya (isi dari direktori, logo wiki /skins/common/images/wiki.png)
 * berkas-berkas konfigurasi, contohnya  dan   (apabila ada)
 * Berkas program MediaWiki, termasuk semua kulit dan ekstensi, khususnya apabila Anda telah mengubahnya.

Menggunakan sebuah paket tarball
Anda bisa menaruh berkas-berkas baru menggunakan FTP atau barisan perintah (command line). Gunakan barisan perintah, apabila Anda bisa mengaksesnya! Menggunakan baris perintah lebih cepat daripada mengunggah setiap berkas melalui FTP.

FTP atau grafis
Jika Anda tidak bisa mengakses baris perintah di peladen Anda, unduh tarball MediaWiki ke komputer lokal Anda dan gunakan 7zip untuk mengekstrak tarball di PC lokal Anda.

Setelah Anda mengekstrak berkasnya secara lokal, gunakan perangkat lunak klien FTP kesukaan Anda untuk mengunggah direktori dan berkas ke peladen Anda.

Baris perintah
Anda mungkin perlu menjalankan perintah sebagai  apabila Anda tidak punya izin menulis penuh ke direktori instalasi wiki menggunakan pengguna Anda yang sekarang. Ketika mengekstrak paket tarball biasanya sebuah direktori baru akan dibuat dan Anda akan punya salinan berkas konfigurasi dan direktori gambar lama dari direktori instalasi lama Anda:

$ cd /path/to/your/new/installation/ $ wget https://releases.wikimedia.org/mediawiki//mediawiki-.tar.gz $ tar -xvzf mediawiki-.tar.gz $ rm mediawiki-.tar.gz

Pengguna (Open)Solaris sebaiknya menggunakan gtar, atau:

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

Berkas lain
Setelah mengekstrak tarball, Anda sebaiknya menyalin atau memindahkan beberapa berkas dan folder dari direktori instalasi yang lama ke yang baru:


 * , yang berisi pengaturan konfigurasi lama Anda.
 * Direktori  (atau   dalam versi yang lebih lama), yang berisi semua berkas yang telah diunggah ke wiki, kecuali Anda memilih direktori pengunggahan yang berbeda, dan ubah kepemilikan dan perizinannya.   dan   (jika misalnya pengguna web Anda adalah apache).
 * Beberapa ekstensi di direktori . Anda sebainya selalu memakai ekstensi yang mutakhir, ekstensi lama tidak dijamin akan bekerja di versi MediaWiki yang lebih baru.
 * Jika Anda menggunakan logo buatan sendiri berkas ini juga perlu dikembalikan dari cadangan. Sebelum 1.24 ini biasanya terletak di . Setelah 1.24 letaknya di   atau   tergantung yang mana yang Anda pilih. Kemduian tambahkan misalnya   ke LocalSettings.php.
 * Kulit-kulit khusus dari dalam direktori.
 * Modifikasi apapun yang dilakukan pada berkas instalasi atau ekstensi yang lama.
 * Berkas .htaccess apapun (apabila Anda menggunakan Apache dan Anda telah mendefinisikan aturan-aturan di dalamnya).

Setelah melakukannya, jadikan folder baru ini folder yang dimuatkan di peladen web, atau ubah nama direktori instalasi yang lama lalu ubah nama direktori yang baru menjadi nama direktori yang lama.

Menggunakan Git
Jika menggunakan, ekspor berkas-berkasnya ke dalam lokasi yang bersih, lalu salin berkas yang dulu pernah disesuaikan ke dalam lokasi baru sebagaimana dijelaskan di bagian sebelumnya.

Anda juga perlu menginstal beberapa pustaka PHP eksternal menggunakan Composer atau kumpulan pustaka yang disediakan dan dipelihara untuk wiki farm Wikimedia. Rincian lebih lanjut mengenai pemasangan dan pembaruan pustaka eksternal bisa ditemukan di dokumentasi unduhan Git.

Menggunakan patch
Berkas patch kecil biasanya disediakan untuk pemutakhiran versi minor. Unduh dan ekstrak berkas patch secara manual dari situs dump atau ikuti petunjuk dengan wget di bawah. Patch bersifat bertahap, Anda tidak bisa melewatkan salah satu versi.


 * 1) cd ke direktori MediaWiki utama Anda (direktori yang berisi LocalSettings.php).
 * 2) Unduh berkas patch dan gunakan gunzip padanya.
 * 3) Gunakan   untuk memeriksa apa yang akan diubah (contoh,  )
 * 4) Jika semuanya berjalan baik, jalankan patch lagi tanpa.
 * 5) Periksa Special:Version Anda dan Anda seharusnya melihat nomor versi yang baru.

Sisa berkas yang mungkin menimbulkan kesalahan
Jika Anda mengekstrak menimpa direktori instalasi yang lama, beberapa berkas lama bisa menyebabkan masalah untuk versi yang baru.

Jika Anda tidak menggunakan profiling, tetapi memiliki berkas  di folder akar MediaWiki, Anda mungkin mendapatkan galat yang merujuk pada. Menghapus, atau mengubah nama, berkas  akan menyelesaikan galat ini. Berkas, juga terletak di folder akar MediaWiki, bisa menjadi templat apabila Anda suatu saat mau mengaktifkan profiling.

MediaWiki 1.23 mengusangkan mekanisme penemuan kulit secara otomatis untuk berkas-berkas kulit inti. Setelah memutakhirkan ke versi ini, Anda sebaiknya memastikan berkas-berkas lama,  ,   dan   di dalam direktori   serta subfolder-subfolder yang bersesuaian di dalam direktori   telah dihapus. MediaWiki akan mengingatkan Anda dengan mencatat peringatan apabila masih ada di antara mereka yang masih ditemukan. (Anda juga perlu menyesuaikan kulit-kulit buatan sendiri agar mengikuti konvensi yang serupa.) Lihat $discover untuk rinciannya.

MediaWiki 1.24 mengubah jalur ke berkas kulit inti. Setelah memutakhirkan ke versi ini, Anda sebaiknya memastikan berkas-berkas lama,  ,   dan   yang ada secara langsung di direktori   tidak lagi ada. Lihat $discover untuk rinciannya.

Memuktahirkan ekstensi
Ekstensi-ekstensi tertentu telah dimutakhirkan agar bekerja dengan versi MediaWiki yang baru. Pastikan untuk memutakhirkan ekstensi-ekstensi tersebut ke versi terkininya. Anda mungkin perlu melakukan pemutakhiran secara manual untuk ekstensi-ekstensi kustom.

Tarball yang berbeda-beda memasukkan beberapa subset dari ekstensi dan memiliki pengelolaan versi yang membantu Anda memilih yang tepat untuk rilis inti MediaWiki Anda.

Extension Distributor bekerja baik untuk kebanyakan orang yang menginginkan cuplikan ekstensi-ekstensi yang akan bekerja pada versi MediaWiki yang didukung.

Jika Anda menginginkan banyak ekstensi maka sebaiknya Anda mengunduh dari Git. Jika Anda tidak punya Git tetapi Anda ingin memperbarui banyak ekstensi, Anda sebaiknya mempertimbangkan untuk menggunakan mwExtUpgrader.

Menyesuaikan LocalSettings.php anda
Jika Anda menggunakan  yang sama dengan versi yang lama, Anda mungkin perlu menyesuaikannya dengan bagaimana versi yang baru menjalankannya:

Pendaftaran kulit
Sejak MediaWiki 1.24, kulit-kulit yang sepaket seperti Vector, Monobook, Modern dan CologneBlue tidak lagi menjadi bagian dari inti MediaWiki, dan perlu didaftarkan secara eksplisit di  agar bisa digunakan, jika tidak MediaWiki akan memperingatkan bahwa Anda tidak memiliki kulit yang telah dipasang.

Ini adalah apa yang perlu Anda tambahkan ke  ketika memutakhirkan dari versi-versi yang lebih lama daripada 1.24 dan menginginkan kulit-kulit tersebut tersedia:

Kulit-kulit lainnya mungkin belum disesuaikan dengan sistem pendaftaran kulit yang baru, jadi rujuklah halaman dokumentasi masing-masing kulit untuk melihat bagaimana cara mendaftarkannya apabila terjadi masalah.

Pendaftaran ekstensi
Sejak MediaWiki 1.25, ekstensi menggunakan sistem pendaftaran ekstensi baru.

Sebelumnya  Anda akan berisi seperti ini:

Ini bisa diubah menjadi:

Ekstensi disesuaikan agar menggunakan sistem pendaftaran ekstensi baru. Ekstensi yang tidak disesuaikan sebaiknya menggunakan cara instalasi yang lama. Rujuklah instruksi instalasi di halaman ekstensi untuk informasi lebih lanjut.

Variabel lainnya
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 backwards compatible. In any case, take a look to the release notes to see those changes.

Menjalankan skrip pemuktahiran
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.

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

Apa yang dilakukan ketika muncul kesalahan "ALTER command denied to user" (atau yang mirip)
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.

Apa yang dilakukan ketika muncul kesalahan "unexpected T_STRING"
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'
 * 2) once you have discerned the location of the php5 path, list the contents of php5/bin directory
 * 3) 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:

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

Apa yang dilakukan ketika muncul kesalahan 'register_argc_argv is set to false'
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.
 * 2) Add a line as follows:

 register_argc_argv=true


 * 1) Re-run php update.php

Peramban web

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


 * 1) Always back up before performing database maintenance.
 * 2) Navigate your webbrowser to  . For example, if your wiki is at , then navigate to.
 * 3) Select your language and click continue.
 * 4) 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 webserver 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.

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

Pertanyaan yang sering diajukan


Seberapa sulit melakukan pemuktahiran?
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.

Bagaimana saya memuktahirkan dari versi yang lama sekali? Dalam satu langkah, atau beberapa langkah?
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 relevant settings file (warning: huge page!) 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, 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, also if you had not skipped versions, but if you had each time done each single update. Only will you - when you skipped versions - get them all at the same time. This will make the upgrade more difficult, but do not forget that you did not have the trouble updating to the intermediate versions, which you skipped!

Apakah sebaiknya saya mencadangkan dulu?
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.

Bisakah saya menyimpan LocalSettings.php saya?
Yes, but you may have to make some minor changes. The format of is largely backwards compatible. Changes which break LocalSettings.php compatibility will be documented in the "configuration changes" section of the release notes.

Bisakah wiki saya tetap dalam jaringan ketika pemuktahiran?
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
 * 2) Prepare that new directory: copy your current LocalSettings.php from the old directory, copy any installed extensions and custom skins (if any). Check  setting in LocalSettings.php and if necessary copy logo file from the old directory to the new directory.
 * 3) In the release notes for the new version, see if any changes need to be made to LocalSettings.php.
 * 4) 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.
 * 2) Run the update script or the web updater in the new directory.
 * 3) Copy the images from the images sub-directory from the old directory to the new directory.
 * 4) Swap the old directory and the new directory.

Mengapa memuktahirkan?

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


 * Since 1.5, edits can be previewed before saving also as diff.
 * Since 1.9, an undo button is available.
 * Since 1.12, patrolling on Special:NewPages is much easier.
 * Since 1.13, you can rename (move) files.
 * Since 1.14, you can fix double redirects automatically.
 * Since 1.16, 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 1.29, the Action API was reworked and improved. Also user group assignments may now be done for a selectable period.

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

Lihat pula

 * Greg Sabino Mullane's Blog post provides some more detail about point release upgrades.
 * Project:Support desk if you need help or something went wrong
 * (if you don't have a successful backup)
 * (if you don't have a successful backup)
 * (if you don't have a successful backup)
 * (if you don't have a successful backup)
 * (if you don't have a successful backup)