Manual:Upgrading/ja

パッケージのダウンロード

安定バージョン (1.24.2)

• mediawiki-1.24.2.tar.gz
• Git ブランチ: REL1_24

旧バージョン (1.23.9)

• mediawiki-1.23.9.tar.gz
• Git ブランチ: REL1_23

アルファ バージョン

• MediaWiki ナイトリー ビルド

---

参考

• ニュース
• Git からのダウンロード
• 1.24.2 へのアップグレード

基本的な概要

ファイル転送

ファイル転送の方法を選択してください:

• Secure copy with SCP or WinSCP
• SSH File Transfer Protocol (SFTP)
• Using a FTP client.
• The hosting company might provide a file manager interface via the web browser; check with your provider.
• Some other method. There is a list of these at Wikipedia:List of file transfer protocols

Preliminary

Read the UPGRADE text file included in MediaWiki.

1. 要件を確認する
2. リリースノートを読む
3. 既存のファイルとデータベースをバックアップする
4. 新バージョンのファイルを展開（解凍）する
5. 拡張機能（エクステンション）をアップグレードする
6. 更新スクリプトを実行してデータベースをチェックする
7. 更新を確認する

システム要件の確認

MediaWiki 1.24 の要件は以下の通りです:

• PHP 5.3.2 以降
• MySQL 5.0.2 以降、PostgreSQL 8.3 以降、SQLite 3.3.7 以降、Oracle 9.0.1 以降のいずれか

PostgreSQL を使用している場合は、Postgres のアップグレードもお読みください。

詳細情報については、システム要件および互換性をお読みください。

リリースノートを読む

Within the distribution tarball, or within the files checked out/exported from Special:MyLanguage/Git, there are a number of files with capitalised filenames, one of which contains the RELEASE-NOTES (ウィキ). Now's the time to open it up and find out what's been changed in this release.

既存のファイルとデータベースをバックアップする

完全な説明書： Manual:Backing up a wiki/ja

アップグレードスクリプトがよく整備され堅牢であるとはいえ、things could still go awry。データベース構造を更新する前に、データベースとファイルの両方を含む、wikiの完全なバックアップを取得してください。

• the wiki's content, from the database, (make sure you get the character set specified correctly, first check LocalSettings.php). It may be a good idea to create an XML dump in addition to the SQL database dump.
  • MySQL:
    • テキストダンプ: mysqldump --all-databases > file.txt
    • xmlダンプ: mysqldump --all-databases --xml > file.xml
  • PostgreSQL:
    • pg_restore の出力: pg_dump --create -Fc -i yourwiki > yourwiki.db.dump
  • SQLite:
    • php maintenance/sqlite.php --backup-to filename
• 画像およびその他のメディアファイル（images ディレクトリの中身、カスタム ロゴ /skins/common/images/wiki.png）
• 設定ファイル、例えば LocalSettings.php および AdminSettings.php （存在する場合）
• MediaWikiのプログラムファイル。すべてのスキン・拡張機能を含む。自分で変更した場合は特に。

新バージョンのファイルを展開する

tar 形式パッケージの使用

You can put the new files into place using FTP or the command line. Use the command line, if you have access to it! Using the command line will be much faster than having to upload each single one of the thousands of files via FTP.

You should put the decompressed tarball in a new and empty folder on your server. If you instead extract the new version directly on top of your old version, rather than in a new directory, you should follow #Back up existing files and the database: otherwise, if you've made any customizations you may erase them in a way that leaves you with no reference to re-apply them from. Extracting a tarball over top of your live copy of MediaWiki can also leave behind files from the old version of MediaWiki which may interfere with the upgraded code. It's recommended that you unpack the new files into a new directory, and then apply customizations to the new directory (restoring LocalSettings.php, images folder, extensions, and other customizations like custom skins)

FTP またはグラフィカル

If you cannot access the command line on your server, download the MediaWiki tarball to your local computer and use 7zip to extract the tarball on your local PC.

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

コマンドライン

You may need to run the command as sudo 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:

$ tar xvzf mediawiki-1.24.2.tar.gz -C /path/to/your/new/installation/

(Open)Solarisユーザーは gtar を使うか、または:

$ gzip -dc mediawiki-1.24.2.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:

• LocalSettings.php, which contains your old configuration settings.
• The images (or uploads 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. chmod -R 755 images and chgrp -R apache images (e.g. if your web user is apache).
• Some extensions in the extension 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 (usually placed in /skins/common/images/).
• Custom skins from within the skins directory.
• Any modifications made to the old installation files.
• 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.

Git の使用

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

パッチの使用

A small patch file is usually made available for a minor version upgrade. Manually download and extract the patch file from the dumps site or follow the directions with wget below.

1. cd to your main MediaWiki directory (the one with LocalSettings.php).
2. Download the patch file and gunzip it.
3. Use patch -p 1 --dry-run to check what will be changed (e.g., patch -p 1 --dry-run < mediawiki-MW stable release number.patch )
4. If all is well, run patch again without --dry-run.
5. 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.

MediaWiki バージョン:

≥ 1.18

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

MediaWiki バージョン:

≥ 1.24

MediaWiki 1.24 will deprecate the skin autodiscovery mechanism and change the paths of core skin files. After upgrading to this version, you should ensure that the old files CologneBlue.php, Modern.php, MonoBook.php and Vector.php directly in the skins/ directory are no longer present. MediaWiki will log warnings if any of them are found to help you remember. (You will also need to adjust any custom skins to follow a similar convention.) See Manual:Skin autodiscovery for details.

拡張機能をアップグレード

拡張機能（エクステンション）の中には、新バージョンのMediaWikiで動作するよう更新されているものがあります。このような拡張機能については、必ず最新バージョンにアップグレードしてください。カスタム拡張機能については、手動で更新する必要があるかもしれません。

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.

更新スクリプトを実行

MediaWikiのデータベースは2つの方法でアップグレードできます: コマンドラインとウェブブラウザーの2つです。サーバにシェルアクセスできるのであれば、タイムアウトや接続の切断によりアップグレード処理が中断する危険性を減らせるため、コマンドラインからのアップグレードを推奨します。

コマンドライン

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 maintenance directory and execute the update script:

$ php maintenance/update.php

On Linux if you get an error try performing same command as root (sudo php maintenance/update.php). Note for simple installations on Windows (e.g. with XAMPP): First make sure that your web server (such as Apache) and your database (such as MySQL) are running. Then run update.php: 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 commandline can use another PHP version than that one which you have when you execute MediaWiki from the webserver. 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 php53. 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; he will surely know.

MediaWikiは既存の構造を検査し、必要応じてテーブルやカラムを追加し、新しいコードで動作するよう構造を更新します。

If you use a Shared database, you should pass the --doshared parameter if you want the shared tables to be updated. Otherwise they won't be touched by the update script.

「No superuser credentials」エラーの対処法

In case the scripts abort with a message:

No superuser credentials could be found. Please provide the details of a user with appropriate
permissions to update the database. See AdminSettings.sample for more details"

This means that you should check that you have defined $wgDBadminuser and $wgDBadminpassword in your LocalSettings.php file (in the main directory). These are the user and password needed by this script in order to access to the database. (Note: Prior to MediaWiki 1.16, these variables were located in AdminSettings.php. This file was removed in 1.16 and the variables were moved to LocalSettings.php.)

「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

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.
2. Add a line as follows:

register_argc_argv=true

1. Re-run php update.php

Web ブラウザー

MediaWiki バージョン:

≥ 1.17

See also update.php

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 backup before performing database maintenance.
2. Navigate your webbrowser to /mw-config/. For example, if your wiki is at http://example.org/w/index.php, then navigate to http://example.org/w/mw-config/.
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 LocalSettings.php file and look for the key assigned to $wgUpgradeKey.

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.

警告:	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!

更新を確認する

アップグレードが完了したら、ブラウザーでwikiを表示し、次の操作が期待どおりに動くか確認します。

• ページの表示
• ページの編集
• ファイルのアップロード
• Special:Versionを開き、バージョン表示が正しいことと拡張機能が存在することを確認します。

よくある質問

アップグレードはどのくらい大変ですか?

自分で修正を加えたファイルが LocalSettings.php のみであり、1.5以降からのアップグレードであれば、作業はとても単純です。人手を伴なう作業量は数分だけです。データベース構造の変更には、データベースの大きさに比例した時間がかかります――何百万ものページがあるwikiでは数時間ですが、典型的な数千ページの大きさであれば普通は数秒で完了します。

同じメジャーバージョン内のマイナーアップグレード、例えば1.13.0から1.13.1へは、データベース構造の変更は全く必要ありません。ただファイルを更新するだけでいいのです。データベースの更新が要らないので、インストーラスクリプトを実行する必要はありません。

1.4以前からのアップグレードは複雑になる可能性があります。UTF-8以外のキャラクタセット（文字コードセット）のサポートが停止となり、テキストの大半を格納する構造が変わったためです。UPGRADE ファイルの関連セクションをお読みください。

MediaWiki のソースコードを修正していて、かつその変更を上書きされたくない場合、アップグレードが困難になります。diff、patch、Meld or WinMerge のようなツールが有用です。メンテナンスされていない拡張機能を使用している場合も、トラブルを引き起こすおそれがあります。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.

Tip: instead of patching your "global" css and js (javascript) files everytime 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.

とても古いバージョンからのアップグレードはどのように行ないますか? 一段階で? 数段階?

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 ($wgUseLatin1 needs to be set to true in your LocalSettings.php for this to work). Next, run update.php, and then set the $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 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 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. 信じがたければメーリングリストのこの投稿をお読みください。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!

If upgrading from a MediaWiki version below 1.19, you may need to add the sha1 field to the revision table manually before running the update script (see bug 48820 and a relevant support desk thread).

最初にバックアップすべきですか？

端的な回答： はい。

長い回答： a) データ量、b) バックアップの作成がどのくらい大変か、c) MySQLのメンテナンスおよび管理にどのくらい自信があるか。それ次第です。

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.

復旧にはたいてい手間がかかります。バックアップを怠った上でアップグレード関連のデータ破損から復旧する手助けをサポートフォーラムのボランティアに求めるのは、感心されることではありません。バックアップに戻した上で、破損の原因となったアップグレードスクリプトの処理のバグを報告できれば、よりよい成果となります。

自分の LocalSettings.php を使い続けられますか？

はい、ただ、小さな変更を加える必要があるかもしれません。LocalSettings.php の書式の大部分は下位互換性があります。LocalSettings.php の互換性が中止となった変更点は、リリースノートの「configuration changes」セクションに書かれています。

アップグレード中もwikiをオンラインのままにできますか？

はい、できます。

MediaWikiのマイナーリリース間のアップグレードであれば、ソースファイルを更新するだけです。

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. 新しいディレクトリの中にMediaWikiの新バージョンを展開します
2. 上記新ディレクトリを整える： 旧ディレクトリから現行の LocalSettings.php をコピー、インストールしてある拡張機能とカスタムスキンをコピーします（もしあれば）。
3. In the release notes for the new version, see if any changes need to be made to LocalSettings.php.
4. 旧ディレクトリの LocalSettings.php で読み取り専用モードを有効にします。
   $wgReadOnly = 'MediaWiki 1.24.2 にアップグレード中';
5. Run the update script or the web updater in the new directory.
   
6. 旧ディレクトリから新ディレクトリへ、images サブディレクトリの画像ファイルをコピーします。
7. 旧ディレクトリと新ディレクトリを入れ替えます。

アップグレードする理由

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 Version lifecycle). 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.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, InstantCommons is available.
• If you have appropriate caching, since 1.17 ResourceLoader optimizes pageload speeds a lot.
• Since 1.17, category sorting makes sense! (especially for non-English letters); extended to 68 languages after 1.21.
• Since 1.18 and 1.19, users of all languages and genders are correctly addressed by the interface and logs (before 1.15, no gender at all).
• In 1.19 the skinning system was reworked making it easier to reuse parts of existing skins in your own skins.
• Since 1.20, diffs are better 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.

See also the list of the most voted fixed issues on bugzilla.

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.

See also

• Project:Support desk if you need help or something went wrong
• Manual:Backing up a wiki
• Manual:Restoring a wiki from backup
• Manual:Moving a wiki
• Manual:Restoring wiki code from cached HTML (if you don't have a successful backup)
• Manual:Installing