• 赤色のリンクは、まだ日本語Codexに存在しないページ・画像です。英語版と併せてご覧ください。(詳細

このWikiはいつでも誰でも編集できます

「WordPress のアップグレード/詳細」の版間の差分

提供: WordPress Codex 日本語版
移動先: 案内検索
(en:Upgrading WordPress Extended 2007年9月25日 (火) 12:46 MichaelH 版)
 
(冒頭・見出しのみ和訳、リンク微調整、カテゴリ付け)
1行目: 1行目:
==Detailed Instructions==
+
{{Notice|要見直し|一旦和訳してから、ページ構成・内容を見直します。}}
  
===Overview of the Upgrade Process===
+
<div id="Detailed_Instructions">
# [[#Step 1: Backup your database|Backup your database]]. Read [[Backing Up Your Database]] for a detailed explanation.
+
== 詳細説明書 ==
# [[#Step 2: Backup ALL your WordPress files|Backup ALL your WordPress files]] in your WordPress directory.  Don't forget your [[Glossary#.htaccess<|<tt>.htaccess</tt>]] file. 
+
</div>
# [[#Step 3: Verify the backups|Verify the backups]] you created are there and usable.  This is essential.   
+
# [[#Step 4: Deactivate ALL your Plugins|Deactivate ALL your Plugins]].
+
# [[#Step 5: Ensure first four steps are completed|Ensure first four steps are completed]].  Do not attempt the upgrade unless you have completed the first four steps.
+
# [[#Step 6: Download and extract the WordPress package|Download and extract the WordPress package]] from http://wordpress.org/download/.
+
# [[#Step 7: Delete the old WordPress files|Delete the old WordPress files]] on your site, but '''<span style="color:red">DO NOT DELETE</span>'''
+
#*<code><span style="color:red">wp-config.php</span></code> file;
+
#*<code><span style="color:red">wp-content</span></code> folder;  Special Exception:  the <code>wp-content/cache</code> and the <code>wp-content/plugins/widgets</code> folders should be deleted.
+
#*<code><span style="color:red">wp-images</span></code> folder;
+
#*<code><span style="color:red">wp-includes/languages/</span></code> folder--if you are using a language file do not delete that folder;
+
#*<code><span style="color:red">.htaccess</span></code> file--if you have added custom rules to your <code>.htaccess</code>, do not delete it;
+
#*<code><span style="color:red">robots.txt</span></code> file--if your blog lives in the root of your site (ie. the blog is the site) and you have created such a file, do not delete it.
+
# [[#Step 8: Upload the new files|Upload the new files]] from your computer's hard drive to the appropriate WordPress folder on your site.
+
# [[#Step 9: Run the WordPress upgrade program|Run the WordPress upgrade program]] and follow the instructions on the screen.
+
# [[#Step 10: Update Permalinks and .htaccess|Update Permalinks and .htaccess]].  Update your Permalink Structure and merge the custom rules, if necessary, into your [[Glossary#.htaccess<|<tt>.htaccess</tt>]] file.
+
# [[#Step 11: Install updated Plugins and Themes|Install updated Plugins and Themes]].  Please review the [[Plugins/Plugin_Compatibility/2.3|list of Plugins that work in Version {{CurrentVersion}}]].  Check for [[Themes/Theme_Compatibility/2.3|Theme Compatibility with {{CurrentVersion}}]] and ask your Theme author for any new version.
+
# [[#Step 12: Reactivate Plugins|Reactivate Plugins]]
+
# [[#Step 13: Review what has changed in WordPress|Review what has changed in WordPress]].
+
  
That's the overview of the upgrade process. Please continue reading the Detailed Upgrade Instructions.
+
<div id="Overview_of_the_Upgrade_Process">
 +
=== 作業の概要 ===
 +
</div>
 +
# [[#Step 1: Backup your database|データベースをバックアップ]]。 詳しい説明は [[:en:Backing Up Your Database|Backing Up Your Database]] をご覧ください。
 +
# WordPress ディレクトリ内の [[#Step 2: Backup ALL your WordPress files|全ての WordPress ファイルをバックアップ]]。[[用語集#.htaccess<|<code>.htaccess</code>]] ファイルをお忘れなく。
 +
# 取得した[[#Step 3: Verify the backups|バックアップの検証]]。ファイルが存在すること、使用可能な状態であるかを必ず確認。
 +
# [[#Step 4: Deactivate ALL your Plugins|全てのプラグインを無効化]]。
 +
# [[#Step 5: Ensure first four steps are completed|上記 4 ステップを確実に完了させる]]。上記 4 ステップが完了するまでは、アップグレードしないでください。
 +
# http://wordpress.org/download/ から [[#Step 6: Download and extract the WordPress package|WordPress パッケージをダウンロード・展開]]。
 +
# サイト上の[[#Step 7: Delete the old WordPress files|旧 WordPress ファイルを削除]]。ただし、次のものは'''<span style="color:red">削除しないでください</span>'''。
 +
#*<code><span style="color:red">wp-config.php</span></code> ファイル
 +
#*<code><span style="color:red">wp-content</span></code> ディレクトリ -- 例外: <code>wp-content/cache</code> ディレクトリおよび <code>wp-content/plugins/widgets</code> ディレクトリは削除すること。
 +
#*<code><span style="color:red">wp-images</span></code> ディレクトリ
 +
#*<code><span style="color:red">wp-includes/languages/</span></code> ディレクトリ -- 言語ファイルを使っている場合、このフォルダは削除しないこと。<!-- 場所変わったかも -->
 +
#*<code><span style="color:red">.htaccess</span></code> ファイル -- <code>.htaccess</code> にカスタムルールを追加している場合、削除しないこと。
 +
#*<code><span style="color:red">robots.txt</span></code> ファイル -- ブログがルートにあって、このファイルを作成している場合、削除しないこと。
 +
# あなたのコンピュータのハードドライブからサイト上の適切な WordPress ディレクトリへ、[[#Step 8: Upload the new files|新ファイルをアップロード]]
 +
# [[#Step 9: Run the WordPress upgrade program|WordPress アップグレードプログラムを実行]]し、画面上の指示に従う。
 +
# [[#Step 10: Update Permalinks and .htaccess|パーマリンクと .htaccess を更新]]。パーマリンク構造を更新し、必要であればカスタムルールを [[用語集#.htaccess|<code>.htaccess</code>]] ファイルへマージ。
 +
# [[#Step 11: Install updated Plugins and Themes|更新済みプラグインとテーマをインストール]]。 [[:en:Plugins/Plugin_Compatibility/2.3|バージョン {{CurrentVersion}} で動作するプラグイン一覧]]を見直してください。[[:en:Themes/Theme_Compatibility/2.3|テーマが {{CurrentVersion}} 互換]]か確認して、載っていなければ、テーマの作者に新バージョンについて尋ねてみましょう。
 +
# [[#Step 12: Reactivate Plugins|プラグインを再び有効化]]。
 +
# [[#Step 13: Review what has changed in WordPress|WordPress の変更点を見直す]]。
  
Remember, if you do encounter problems, re-read the Instructions below to insure you've followed the proper procedures and consult  [[Installing_WordPress#Common_Installation_Problems|Troubleshooting: Common Installation Problems]].
+
以上がアップグレード作業の概要です。続けてアップグレード手順の詳細をお読みください。
  
===Detailed Upgrade Instructions for 1.5.x, 2.0.x, 2.1.x, or 2.2.x to {{CurrentVersion}}===
+
Remember, if you do encounter problems, re-read the Instructions below to insure you've followed the proper procedures and consult [[WordPress のインストール#Common_Installation_Problems|Troubleshooting: Common Installation Problems]].
The following are the instructions that explain the above steps in more detail. Please read all of the instructions before starting.
+
  
====Step 1: Back up your database====
+
<div id="Detailed_Upgrade_Instructions_for_1.5.x,_2.0.x,_2.1.x,_or_2.2.x_to_{{CurrentVersion}}">
Perform a backup of your database.  All of your WordPress data, such as Users, Posts, Pages, Links, and Categories, are stored in your [[Glossary#MySQL|MySQL]] [[Database Description|database]].  Please read [[Backing Up Your Database]] for a detailed explanation of this process.  
+
=== 1.5.x, 2.0.x, 2.1.x, or 2.2.x から {{CurrentVersion}} へのアップグレード手順詳細 ===
 +
</div>
 +
上記手順の詳細を説明したガイドは以下のとおりです。作業を始める前に、説明の全てに目を通しておいてください。
 +
 
 +
<div id="Step_1:_Back_up_your_database">
 +
==== 手順 1: データベースをバックアップ ====
 +
</div>
 +
Perform a backup of your database.  All of your WordPress data, such as Users, Posts, Pages, Links, and Categories, are stored in your [[用語集#MySQL|MySQL]] [[データベース概要|database]].  Please read [[:en:Backing Up Your Database|Backing Up Your Database]] for a detailed explanation of this process.  
  
 
It is extremely important to back up your database before beginning the upgrade.  If, for some reason, you find it necessary to revert back to the 'old' version of WordPress, you may have to restore your database from these backups.
 
It is extremely important to back up your database before beginning the upgrade.  If, for some reason, you find it necessary to revert back to the 'old' version of WordPress, you may have to restore your database from these backups.
  
====Step 2: Back up ALL your WordPress files====
+
<div id="Step_2:_Back_up_ALL_your_WordPress_files">
Back up ALL of your files in your WordPress directory and your [[Glossary#.htaccess<|<tt>.htaccess</tt>]] file.  Typically, this process involves using an [[FTP Clients|FTP program]] to download ALL your WordPress files from your host to your local computer.
+
==== 手順 2: 全ての WordPress ファイルをバックアップ ====
Please read [[WordPress_Backups#Backing_Up_Your_WordPress_Site|Backing Up Your WordPress Site]] for further explanation.
+
</div>
 +
Back up ALL of your files in your WordPress directory and your [[用語集#.htaccess<|<tt>.htaccess</tt>]] file.  Typically, this process involves using an [[:en:FTP Clients|FTP program]] to download ALL your WordPress files from your host to your local computer.
 +
Please read [[:en:WordPress_Backups#Backing_Up_Your_WordPress_Site|Backing Up Your WordPress Site]] for further explanation.
  
 
If you have made changes to any core WordPress files, or if you've got customized Plugins or Themes, you will want to have a good backup of those files.  It is extremely important to back up your files before beginning the upgrade.  If for some reason you find it necessary to revert back to the 'old' version of WordPress you will need to upload these files.
 
If you have made changes to any core WordPress files, or if you've got customized Plugins or Themes, you will want to have a good backup of those files.  It is extremely important to back up your files before beginning the upgrade.  If for some reason you find it necessary to revert back to the 'old' version of WordPress you will need to upload these files.
  
====Step 3: Verify the backups====
+
<div id="Step_3:_Verify_the_backups">
 +
==== 手順 3: バックアップの検証 ====
 +
</div>
 
Verify that the backups you created are there and usable.  '''This is the most important step in the upgrade process!'''   
 
Verify that the backups you created are there and usable.  '''This is the most important step in the upgrade process!'''   
 
The verification process involves making sure you can see the backup files on your local computer (or wherever you've stored them) and that you can navigate into any sub-folders.  If the files are in a zip file, make sure you can open the zip file.  
 
The verification process involves making sure you can see the backup files on your local computer (or wherever you've stored them) and that you can navigate into any sub-folders.  If the files are in a zip file, make sure you can open the zip file.  
  
====Step 4: Deactivate ALL your Plugins====
+
<div id="Step_4:_Deactivate_ALL_your_Plugins">
In your [[Administration Panels|Administration panel]], under the Plugins choice, deactivate any Plugins.  Because of the changes to WordPress, some Plugins may conflict with the upgrade process.
+
==== 手順 4: 全てのプラグインを無効化 ====
 +
</div>
 +
In your [[管理パネル|Administration panel]], under the Plugins choice, deactivate any Plugins.  Because of the changes to WordPress, some Plugins may conflict with the upgrade process.
  
====Step 5: Ensure first four steps are completed====
+
<div id="Step_5:_Ensure_first_four_steps_are_completed">
 +
==== 手順 5: 上記 5 ステップを確実に完了させる ====
 +
</div>
 
If you have not completed the first four procedures, STOP, and do them!  Do not attempt the upgrade unless you have completed the first four steps.   
 
If you have not completed the first four procedures, STOP, and do them!  Do not attempt the upgrade unless you have completed the first four steps.   
  
 
The best resource for problems with your upgrade is the [http://wordpress.org/support/ WordPress Support Forums], and if you have problems, the volunteers at the [http://wordpress.org/support/ WordPress Support Forums] will likely ask if you have completed the first four steps.
 
The best resource for problems with your upgrade is the [http://wordpress.org/support/ WordPress Support Forums], and if you have problems, the volunteers at the [http://wordpress.org/support/ WordPress Support Forums] will likely ask if you have completed the first four steps.
  
====Step 6: Download and extract the WordPress package====
+
<div id="Step_6:_Download_and_extract_the_WordPress_package">
 +
==== 手順 6: WordPress パッケージをダウンロード・展開 ====
 +
</div>
 
Download and unzip the WordPress package from http://wordpress.org/download/.
 
Download and unzip the WordPress package from http://wordpress.org/download/.
 
* If you will be uploading WordPress to a remote web server, download the WordPress package to your computer with your favorite web browser and unzip the package.
 
* If you will be uploading WordPress to a remote web server, download the WordPress package to your computer with your favorite web browser and unzip the package.
* If you have [[Glossary#Shell|shell]] access to your web server, and are comfortable using console-based tools, you may wish to download WordPress directly to your [[Glossary#Web server|web server]]. You can do so using <tt>wget</tt> , <tt>lynx</tt> or another console-based web browser, which are valuable if you want to avoid [[Glossary#FTP|FTPing]]. Place the package in a directory parallel to your current wordpress directory (like "uploads," for example). Then, unzip it using: <tt>gunzip -c wordpress-{{CurrentVersion}}.tar.gz | tar -xf -</tt> or by using: <tt>tar -xzvf latest.tar.gz </tt>  
+
* If you have [[用語集#Shell|shell]] access to your web server, and are comfortable using console-based tools, you may wish to download WordPress directly to your [[用語集#Web server|web server]]. You can do so using <tt>wget</tt> , <tt>lynx</tt> or another console-based web browser, which are valuable if you want to avoid [[用語集#FTP|FTPing]]. Place the package in a directory parallel to your current wordpress directory (like "uploads," for example). Then, unzip it using: <tt>gunzip -c wordpress-{{CurrentVersion}}.tar.gz | tar -xf -</tt> or by using: <tt>tar -xzvf latest.tar.gz </tt>  
  
 
The WordPress package will be extracted into a folder called <tt>wordpress</tt>.
 
The WordPress package will be extracted into a folder called <tt>wordpress</tt>.
  
====Step 7: Delete the old WordPress files====
+
<div id="Step_7:_Delete_the_old_WordPress_files">
 +
==== 手順 7: 旧 WordPress ファイルを削除 ====
 +
</div>
 
'''Why Delete?''' Generally, it is a good idea to delete whatever is possible because the uploading (or upgrading through cPanel) process may not correctly overwrite an existing file and that may cause problems later.
 
'''Why Delete?''' Generally, it is a good idea to delete whatever is possible because the uploading (or upgrading through cPanel) process may not correctly overwrite an existing file and that may cause problems later.
  
78行目: 100行目:
 
'''How to Delete?''' There are several ways to delete the files from your WordPress site.  You can use your FTP Client, or if you have access to Telenet or SSH you can use that.  Some host providers also provide the ability to delete files and folders.
 
'''How to Delete?''' There are several ways to delete the files from your WordPress site.  You can use your FTP Client, or if you have access to Telenet or SSH you can use that.  Some host providers also provide the ability to delete files and folders.
  
;Using FTP to delete files and folders :The same [[FTP_Clients|FTP client]] you use for [[Uploading_WordPress_to_a_remote_host|uploading]] can be used to delete files and folders.  If your [[FTP_Clients|FTP client]] does not appear to permit you to delete non-empty folders, check the available options for your [[FTP_Clients|FTP client]]. You'll usually find an option that permits deleting non-empty folders. Deleting non-empty folders is a quick and thorough method cleaning out an old installation of WordPress.  It is recommended that once the deleting is done, you switch back to the original setting for safety reasons.
+
;Using FTP to delete files and folders :The same [[:en:FTP_Clients|FTP client]] you use for [[:en:Uploading_WordPress_to_a_remote_host|uploading]] can be used to delete files and folders.  If your [[:en:FTP_Clients|FTP client]] does not appear to permit you to delete non-empty folders, check the available options for your [[:en:FTP_Clients|FTP client]]. You'll usually find an option that permits deleting non-empty folders. Deleting non-empty folders is a quick and thorough method cleaning out an old installation of WordPress.  It is recommended that once the deleting is done, you switch back to the original setting for safety reasons.
  
 
;Using Telnet or SSH to delete file :If you have a command-line login (telnet or ssh), you can enter the following commands to make backup copies of the files you need to keep and to delete ONLY the wordpress files in your directory (plus .htaccess). If you've customized other files (like <code>index.php</code>) not included by the <code>cp</code> commands below, copy them as well:
 
;Using Telnet or SSH to delete file :If you have a command-line login (telnet or ssh), you can enter the following commands to make backup copies of the files you need to keep and to delete ONLY the wordpress files in your directory (plus .htaccess). If you've customized other files (like <code>index.php</code>) not included by the <code>cp</code> commands below, copy them as well:
90行目: 112行目:
 
: Alternatively, using SSH, you could copy <code>wp-config.php, .htaccess</code>, and any content files you've added or altered into the ''new'' wordpress directory. Then, rename the old one (to archive it), and move the new one into its place.
 
: Alternatively, using SSH, you could copy <code>wp-config.php, .htaccess</code>, and any content files you've added or altered into the ''new'' wordpress directory. Then, rename the old one (to archive it), and move the new one into its place.
  
====Step 8: Upload the new files====
+
<div id="Step_8:_Upload_the_new_files">
With the new upgrade on your local computer, and using [[Glossary#FTP|FTP]], [[Uploading_WordPress_to_a_remote_host|upload]] the new files to your site server just as you did when you first installed WordPress.  See [[Using FileZilla|Using FileZilla]] and [[Uploading_WordPress_to_a_remote_host|Uploading WordPress to a remote host]] for  detailed guidelines in using an FTP Client to upload.
+
==== 手順 8: 新ファイルをアップロード ====
 +
</div>
 +
With the new upgrade on your local computer, and using [[用語集#FTP|FTP]], [[:en:Uploading_WordPress_to_a_remote_host|upload]] the new files to your site server just as you did when you first installed WordPress.  See [[:en:Using FileZilla|Using FileZilla]] and [[:en:Uploading_WordPress_to_a_remote_host|Uploading WordPress to a remote host]] for  detailed guidelines in using an FTP Client to upload.
  
 
'''NOTE: If you did not delete the <code>wp-content</code> folder, you will need to overwrite some files during the upload.'''  
 
'''NOTE: If you did not delete the <code>wp-content</code> folder, you will need to overwrite some files during the upload.'''  
99行目: 123行目:
 
The WordPress default theme has changed so you will want to upload the <code>wp-content/themes/default</code> folder.  If you have custom changes to the default theme, those changes will need to be reviewed and installed after the upgrade.
 
The WordPress default theme has changed so you will want to upload the <code>wp-content/themes/default</code> folder.  If you have custom changes to the default theme, those changes will need to be reviewed and installed after the upgrade.
  
====Step 9: Run the WordPress upgrade program====
+
<div id="Step_9:_Run_the_WordPress_upgrade_program">
 +
==== 手順 9:WordPress アップグレードプログラムを実行 ====
 +
</div>
 
Run the WordPress upgrade script by accessing <tt>wp-admin/upgrade.php</tt> in your favorite web browser and follow the instructions presented on your screen.
 
Run the WordPress upgrade script by accessing <tt>wp-admin/upgrade.php</tt> in your favorite web browser and follow the instructions presented on your screen.
 
* If WordPress is installed in the root directory, point your browser to: <tt><nowiki>http://example.com/wp-admin/upgrade.php</nowiki></tt>
 
* If WordPress is installed in the root directory, point your browser to: <tt><nowiki>http://example.com/wp-admin/upgrade.php</nowiki></tt>
 
* If WordPress is installed in its own subdirectory called <tt>blog</tt>, for example, point your browser to: <tt><nowiki>http://example.com/blog/wp-admin/upgrade.php</nowiki></tt>
 
* If WordPress is installed in its own subdirectory called <tt>blog</tt>, for example, point your browser to: <tt><nowiki>http://example.com/blog/wp-admin/upgrade.php</nowiki></tt>
  
====Step 10: Update Permalinks and .htaccess====
+
<div id="Step_10:_Update_Permalinks_and_.htaccess">
In your [[Permalinks_Options_SubPanel|Options->Permalinks]] panel update your Permalink Structure and, if necessary, place the rules in your [[Glossary#.htaccess<|<tt>.htaccess</tt>]] file.  Also see [[Using_Permalinks|Using Permalinks]] for details regarding Permalinks and the [[Glossary#.htaccess<|<tt>.htaccess</tt>]] file.
+
==== 手順 10:パーマリンクと .htaccess を更新 ====
 +
</div>
 +
In your [[:en:Permalinks_Options_SubPanel|Options->Permalinks]] panel update your Permalink Structure and, if necessary, place the rules in your [[用語集#.htaccess<|<tt>.htaccess</tt>]] file.  Also see [[パーマリンクの使い方|Using Permalinks]] for details regarding Permalinks and the [[用語集#.htaccess<|<tt>.htaccess</tt>]] file.
  
====Step 11: Install updated Plugins and Themes====
+
<div id="Step_11:_Install_updated_Plugins_and_Themes">
Please review the [[Plugins/Plugin_Compatibility/2.2|list of Plugins that work in Version 2.2.x]].  You will want to upload and install any new versions of your Plugins and Themes.  Check with the author of those Plugins and Themes for the updated versions.
+
==== 手順 11: 更新済みプラグインとテーマをインストール ====
 +
</div>
 +
Please review the [[:en:Plugins/Plugin_Compatibility/2.2|list of Plugins that work in Version 2.2.x]].  You will want to upload and install any new versions of your Plugins and Themes.  Check with the author of those Plugins and Themes for the updated versions.
  
====Step 12: Reactivate Plugins====
+
<div id="Step_12:_Reactivate_Plugins">
 +
==== 手順 12: プラグインを再び有効化 ====
 +
</div>
 
Use your Administration Panel, Plugins, to activate your Plugins.   
 
Use your Administration Panel, Plugins, to activate your Plugins.   
<!--Please note that if you are using the new WordPress Database Backup Plugin you may need to change the permissions on your <code>wp-content</code> folder to make it writeable by your webserver (either mode 666 or even 777).  See [[Changing_File_Permissions|Changing File Permissions]] for more details.
+
<!--Please note that if you are using the new WordPress Database Backup Plugin you may need to change the permissions on your <code>wp-content</code> folder to make it writeable by your webserver (either mode 666 or even 777).  See [[:en:Changing_File_Permissions|Changing File Permissions]] for more details.
 
-->
 
-->
  
====Step 13: Review what has changed in WordPress====
+
<div id="Step_13:_Review_what_has_changed_in_WordPress">
 +
==== 手順 13: WordPress の変更点を見直す ====
 +
</div>
 
Please review these resources to see what's new in WordPress:   
 
Please review these resources to see what's new in WordPress:   
  
*[[Version_2.3|Version 2.3 Details]]
+
*[[Version 2.3|Version 2.3 Details]]
 
*[http://wordpress.org/development/2007/09/wordpress-23/ WordPress Development Blog: WordPress 2.3 Announcement]
 
*[http://wordpress.org/development/2007/09/wordpress-23/ WordPress Development Blog: WordPress 2.3 Announcement]
  
=====Special note for Fantastico Upgrades=====
+
<div id="Special_note_for_Fantastico_Upgrades">
When using the Fantastico upgrade process to upgrade from a pre-Version 2.2, Fantastico will use the wp-config-sample.php file to regenerate a new wp-config.php file.  By doing this, two new values, DB_CHARSET and DB_COLLATE, are placed into the wp-config.php file.  Those lines should be deleted from your wp-config.php if you are upgrading from a pre-Version 2.2 (like 2.0.10 or 2.1.3) to Version {{CurrentVersion}}.  A detailed explanation about DB_CHARSET and DB_COLLATE can be found in [[Editing wp-config.php]].
+
===== Special note for Fantastico Upgrades =====
 +
</div>
 +
When using the Fantastico upgrade process to upgrade from a pre-Version 2.2, Fantastico will use the wp-config-sample.php file to regenerate a new wp-config.php file.  By doing this, two new values, DB_CHARSET and DB_COLLATE, are placed into the wp-config.php file.  Those lines should be deleted from your wp-config.php if you are upgrading from a pre-Version 2.2 (like 2.0.10 or 2.1.3) to Version {{CurrentVersion}}.  A detailed explanation about DB_CHARSET and DB_COLLATE can be found in [[wp-config.php の編集|Editing wp-config.php]].
  
 
<!-- saving for later upgrades
 
<!-- saving for later upgrades
148行目: 184行目:
 
-->
 
-->
  
==Other languages==
+
<div id="Other_languages">
 +
== 他言語 ==
 +
</div>
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
173行目: 211行目:
 
* [http://bemike.org/blog/2007/01/07/upgrading-wodpress-from-205-to-206.html 简体中文:升级 WordPress 2.0.5 到 2.0.6 的步骤]
 
* [http://bemike.org/blog/2007/01/07/upgrading-wodpress-from-205-to-206.html 简体中文:升级 WordPress 2.0.5 到 2.0.6 的步骤]
  
==Troubleshooting==
+
<div id="Troubleshooting">
;Scrambled Layout or Errors :If your blog looks scrambled now or features line errors, an old plugin that doesn't work with the new code may be the culprit. In your WordPress [[Administration_Panels|Administration Panel]], deactivate all plugins that do not come with WordPress by default. Re-activate them one by one.
+
== トラブルシューティング ==
;Made Custom Changes/Hacks? :If you have made changes to other WordPress files ("hacked" WordPress), you are supposed to keep track of your changes. You will have to transfer your edits into the new code. [[WordPress Versions]] lists the files that have changed in each release.
+
</div>
 +
;Scrambled Layout or Errors :If your blog looks scrambled now or features line errors, an old plugin that doesn't work with the new code may be the culprit. In your WordPress [[管理パネル|Administration Panel]], deactivate all plugins that do not come with WordPress by default. Re-activate them one by one.
 +
;Made Custom Changes/Hacks? :If you have made changes to other WordPress files ("hacked" WordPress), you are supposed to keep track of your changes. You will have to transfer your edits into the new code. [[:en:WordPress Versions|WordPress Versions]] lists the files that have changed in each release.
 
;Resist Using Old Code :Upgrading gives you the newest and best code. Using your old code, no matter how  much you have customised it, almost certainly will cause problems. The temptation just to use your old modified code will be great, but the chances of errors are much greater.
 
;Resist Using Old Code :Upgrading gives you the newest and best code. Using your old code, no matter how  much you have customised it, almost certainly will cause problems. The temptation just to use your old modified code will be great, but the chances of errors are much greater.
;Can I Go Back to Old Versions :You can, but it is usually not recommended to rollback (revert) your current version to an older version. That is because newer versions often include security updates and a rollback may put your site at risk. Second, the change between the database structure between versions may cause complications in maintaining your site content, posts, comments, and plugins that are dependent upon the information stored in the database. If you are still intent on this, proceed at your own risk. '''Please note, that without a backup of your entire site and your database, made prior to your upgrade attempt, a successful rollback is near impossible.''' Delete all WordPress files except for <tt>wp-config</tt>. [[Uploading_WordPress_to_a_remote_host|Upload]] the files from your backup to your server and [[Restoring_Your_Database_From_Backup|restore your database backup]]. Remember, you must have good backups for the rollback to work.  For older WordPress versions, a rollback might not work.
+
;Can I Go Back to Old Versions :You can, but it is usually not recommended to rollback (revert) your current version to an older version. That is because newer versions often include security updates and a rollback may put your site at risk. Second, the change between the database structure between versions may cause complications in maintaining your site content, posts, comments, and plugins that are dependent upon the information stored in the database. If you are still intent on this, proceed at your own risk. '''Please note, that without a backup of your entire site and your database, made prior to your upgrade attempt, a successful rollback is near impossible.''' Delete all WordPress files except for <tt>wp-config</tt>. [[:en:Uploading_WordPress_to_a_remote_host|Upload]] the files from your backup to your server and [[:en:Restoring_Your_Database_From_Backup|restore your database backup]]. Remember, you must have good backups for the rollback to work.  For older WordPress versions, a rollback might not work.
;Get More Help :If you get any errors following an upgrade, check [[Installing_WordPress#Common_Installation_Problems|Troubleshooting: Common Installation Problems]], [[Troubleshooting]], and the [http://codex.wordpress.org/Category:Installation Codex Installation Category of Articles].  If you can't find an answer, post a clear question on the [http://www.wordpress.org/support WordPress Suppport Forums]. You will be asked if you have used any old code. You'll be told to change it then, so you may as well change it now :)
+
;Get More Help :If you get any errors following an upgrade, check [[WordPress のインストール#Common_Installation_Problems|Troubleshooting: Common Installation Problems]], [[:en:Troubleshooting|Troubleshooting]], and the [http://codex.wordpress.org/Category:Installation Codex Installation Category of Articles].  If you can't find an answer, post a clear question on the [http://www.wordpress.org/support WordPress Suppport Forums]. You will be asked if you have used any old code. You'll be told to change it then, so you may as well change it now :)
  
==Old Upgrade Information==
+
<div id="Old_Upgrade_Information">
If you are considering upgrading to WordPress Version {{CurrentVersion}}, but you are at Version 1.2, then follow the 1.2 to 1.5 upgrade as describe in [[Upgrade_1.2_to_1.5|Upgrading From WordPress Version 1.2 to 1.5]].  Once you are upgraded to Version 1.5.x, then follow the instructions as listed above to upgrade from 1.5 to {{CurrentVersion}}.
+
== 過去のアップグレード情報 ==
 +
</div>
 +
If you are considering upgrading to WordPress Version {{CurrentVersion}}, but you are at Version 1.2, then follow the 1.2 to 1.5 upgrade as describe in [[:en:Upgrade_1.2_to_1.5|Upgrading From WordPress Version 1.2 to 1.5]].  Once you are upgraded to Version 1.5.x, then follow the instructions as listed above to upgrade from 1.5 to {{CurrentVersion}}.
  
 
{{原文|Upgrading WordPress Extended}}
 
{{原文|Upgrading WordPress Extended}}
 +
 +
{{DEFAULTSORT:あつふくれえとしようさい}}
 +
[[Category:設置]]
 +
[[Category:初心者向けトピック]]
 +
[[Category:UI Link]]
  
 
[[en:Upgrading WordPress Extended]]
 
[[en:Upgrading WordPress Extended]]

2007年9月29日 (土) 23:08時点における版

要見直し: 一旦和訳してから、ページ構成・内容を見直します。このページのノートをご覧ください。

作業の概要

  1. データベースをバックアップ。 詳しい説明は Backing Up Your Database をご覧ください。
  2. WordPress ディレクトリ内の 全ての WordPress ファイルをバックアップ.htaccess ファイルをお忘れなく。
  3. 取得したバックアップの検証。ファイルが存在すること、使用可能な状態であるかを必ず確認。
  4. 全てのプラグインを無効化
  5. 上記 4 ステップを確実に完了させる。上記 4 ステップが完了するまでは、アップグレードしないでください。
  6. http://wordpress.org/download/ から WordPress パッケージをダウンロード・展開
  7. サイト上の旧 WordPress ファイルを削除。ただし、次のものは削除しないでください
    • wp-config.php ファイル
    • wp-content ディレクトリ -- 例外: wp-content/cache ディレクトリおよび wp-content/plugins/widgets ディレクトリは削除すること。
    • wp-images ディレクトリ
    • wp-includes/languages/ ディレクトリ -- 言語ファイルを使っている場合、このフォルダは削除しないこと。
    • .htaccess ファイル -- .htaccess にカスタムルールを追加している場合、削除しないこと。
    • robots.txt ファイル -- ブログがルートにあって、このファイルを作成している場合、削除しないこと。
  8. あなたのコンピュータのハードドライブからサイト上の適切な WordPress ディレクトリへ、新ファイルをアップロード
  9. WordPress アップグレードプログラムを実行し、画面上の指示に従う。
  10. パーマリンクと .htaccess を更新。パーマリンク構造を更新し、必要であればカスタムルールを .htaccess ファイルへマージ。
  11. 更新済みプラグインとテーマをインストールバージョン 5.3 で動作するプラグイン一覧を見直してください。テーマが 5.3 互換か確認して、載っていなければ、テーマの作者に新バージョンについて尋ねてみましょう。
  12. プラグインを再び有効化
  13. WordPress の変更点を見直す

以上がアップグレード作業の概要です。続けてアップグレード手順の詳細をお読みください。

Remember, if you do encounter problems, re-read the Instructions below to insure you've followed the proper procedures and consult Troubleshooting: Common Installation Problems.

1.5.x, 2.0.x, 2.1.x, or 2.2.x から 5.3 へのアップグレード手順詳細

上記手順の詳細を説明したガイドは以下のとおりです。作業を始める前に、説明の全てに目を通しておいてください。

手順 1: データベースをバックアップ

Perform a backup of your database. All of your WordPress data, such as Users, Posts, Pages, Links, and Categories, are stored in your MySQL database. Please read Backing Up Your Database for a detailed explanation of this process.

It is extremely important to back up your database before beginning the upgrade. If, for some reason, you find it necessary to revert back to the 'old' version of WordPress, you may have to restore your database from these backups.

手順 2: 全ての WordPress ファイルをバックアップ

Back up ALL of your files in your WordPress directory and your .htaccess file. Typically, this process involves using an FTP program to download ALL your WordPress files from your host to your local computer. Please read Backing Up Your WordPress Site for further explanation.

If you have made changes to any core WordPress files, or if you've got customized Plugins or Themes, you will want to have a good backup of those files. It is extremely important to back up your files before beginning the upgrade. If for some reason you find it necessary to revert back to the 'old' version of WordPress you will need to upload these files.

手順 3: バックアップの検証

Verify that the backups you created are there and usable. This is the most important step in the upgrade process! The verification process involves making sure you can see the backup files on your local computer (or wherever you've stored them) and that you can navigate into any sub-folders. If the files are in a zip file, make sure you can open the zip file.

手順 4: 全てのプラグインを無効化

In your Administration panel, under the Plugins choice, deactivate any Plugins. Because of the changes to WordPress, some Plugins may conflict with the upgrade process.

手順 5: 上記 5 ステップを確実に完了させる

If you have not completed the first four procedures, STOP, and do them! Do not attempt the upgrade unless you have completed the first four steps.

The best resource for problems with your upgrade is the WordPress Support Forums, and if you have problems, the volunteers at the WordPress Support Forums will likely ask if you have completed the first four steps.

手順 6: WordPress パッケージをダウンロード・展開

Download and unzip the WordPress package from http://wordpress.org/download/.

  • If you will be uploading WordPress to a remote web server, download the WordPress package to your computer with your favorite web browser and unzip the package.
  • If you have shell access to your web server, and are comfortable using console-based tools, you may wish to download WordPress directly to your web server. You can do so using wget , lynx or another console-based web browser, which are valuable if you want to avoid FTPing. Place the package in a directory parallel to your current wordpress directory (like "uploads," for example). Then, unzip it using: gunzip -c wordpress-5.3.tar.gz | tar -xf - or by using: tar -xzvf latest.tar.gz

The WordPress package will be extracted into a folder called wordpress.

手順 7: 旧 WordPress ファイルを削除

Why Delete? Generally, it is a good idea to delete whatever is possible because the uploading (or upgrading through cPanel) process may not correctly overwrite an existing file and that may cause problems later.

DO NOT DELETE these folders and files:

  • wp-config.php file;
  • wp-content folder;
  • wp-images folder;
  • wp-includes/languages/ folder--if you are using a language file, do not delete this folder;.
  • .htaccess file--if you have added custom rules to your .htaccess, do not delete it;
  • Custom Content and/or Plugins--if you have any images or other custom content or Plugins inside the wp-content folder, do NOT delete them.

Delete these Files and Folders:

  • wp-* (except for those above), readme.html, wp.php, xmlrpc.php, and license.txt; files; Typically files in your root or wordpress folder. Again, don't delete the wp-config.php file.
  • wp-admin folder;
  • wp-includes folder; If using a language file remember don't delete the wp-includes/languages/ folder
  • wp-content/cache folder; You only see this folder if you are upgrading FROM WordPress 2.0.
  • wp-content/plugins/widgets folder; You only see this folder if you previously installed the Sidebar Widgets plugin. The Sidebar Widgets code conflicts with the built-in widget ability.

How to Delete? There are several ways to delete the files from your WordPress site. You can use your FTP Client, or if you have access to Telenet or SSH you can use that. Some host providers also provide the ability to delete files and folders.

Using FTP to delete files and folders 
The same FTP client you use for uploading can be used to delete files and folders. If your FTP client does not appear to permit you to delete non-empty folders, check the available options for your FTP client. You'll usually find an option that permits deleting non-empty folders. Deleting non-empty folders is a quick and thorough method cleaning out an old installation of WordPress. It is recommended that once the deleting is done, you switch back to the original setting for safety reasons.
Using Telnet or SSH to delete file 
If you have a command-line login (telnet or ssh), you can enter the following commands to make backup copies of the files you need to keep and to delete ONLY the wordpress files in your directory (plus .htaccess). If you've customized other files (like index.php) not included by the cp commands below, copy them as well:
  • mkdir backup
  • cp wp-config.php .htaccess backup
  • cp -R wp-content backup
  • rm wp*.php .htaccess license.txt readme.html xmlrpc.php
  • rm -rf wp-admin wp-includes
  • cp backup/wp-config.php .
  • After you have finished with the upgrade, you can restore any customizations to your templates or plugins from your backup directory. For example, use cp backup/index.php . to restore index.php.
Alternatively, using SSH, you could copy wp-config.php, .htaccess, and any content files you've added or altered into the new wordpress directory. Then, rename the old one (to archive it), and move the new one into its place.

手順 8: 新ファイルをアップロード

With the new upgrade on your local computer, and using FTP, upload the new files to your site server just as you did when you first installed WordPress. See Using FileZilla and Uploading WordPress to a remote host for detailed guidelines in using an FTP Client to upload.

NOTE: If you did not delete the wp-content folder, you will need to overwrite some files during the upload.

The wp-content folder holds your WordPress Themes and Plugins. These should remain. Upload everything else first, then upload only those WordPress files that are new or changed to your new wp-content folder. Overwrite any old versions of default plugins with the new ones.

The WordPress default theme has changed so you will want to upload the wp-content/themes/default folder. If you have custom changes to the default theme, those changes will need to be reviewed and installed after the upgrade.

手順 9:WordPress アップグレードプログラムを実行

Run the WordPress upgrade script by accessing wp-admin/upgrade.php in your favorite web browser and follow the instructions presented on your screen.

  • If WordPress is installed in the root directory, point your browser to: http://example.com/wp-admin/upgrade.php
  • If WordPress is installed in its own subdirectory called blog, for example, point your browser to: http://example.com/blog/wp-admin/upgrade.php

In your Options->Permalinks panel update your Permalink Structure and, if necessary, place the rules in your .htaccess file. Also see Using Permalinks for details regarding Permalinks and the .htaccess file.

手順 11: 更新済みプラグインとテーマをインストール

Please review the list of Plugins that work in Version 2.2.x. You will want to upload and install any new versions of your Plugins and Themes. Check with the author of those Plugins and Themes for the updated versions.

手順 12: プラグインを再び有効化

Use your Administration Panel, Plugins, to activate your Plugins.

手順 13: WordPress の変更点を見直す

Please review these resources to see what's new in WordPress:

Special note for Fantastico Upgrades

When using the Fantastico upgrade process to upgrade from a pre-Version 2.2, Fantastico will use the wp-config-sample.php file to regenerate a new wp-config.php file. By doing this, two new values, DB_CHARSET and DB_COLLATE, are placed into the wp-config.php file. Those lines should be deleted from your wp-config.php if you are upgrading from a pre-Version 2.2 (like 2.0.10 or 2.1.3) to Version 5.3. A detailed explanation about DB_CHARSET and DB_COLLATE can be found in Editing wp-config.php.


他言語

Language (english, native) Version (new to old) Remark
Chinese, 简体中文 2.2.1 to 2.2.2, 2.1 to 2.2, 2.1.2 to 2.1.3, 2.1 to 2.1.1, 2.0.7 to 2.0.9, 2.0.6 to 2.0.7, 2.0.4 to 2.0.5
Hungarian, magyar nyelv 2.1.2 to 2.1.3, 2.x to 2.1, none specified
Italian, italiano none specified, none specified
Spain, Castellano 2.2 to 2.2.1, 2.2.1 to 2.2.2
Thai, ภาษาไทย 2.0.3 to 2.0.4
Turkish, Türkçe none specified, none specified
Ukrainian, украї́нська мо́ва 2.0.x to 2.1, 2.0.5 to 2.0.6, 2.0.4 and 2.0.5 to 2.0.6, 2.0.4 to 2.0.5

Unidentified languages

トラブルシューティング

Scrambled Layout or Errors 
If your blog looks scrambled now or features line errors, an old plugin that doesn't work with the new code may be the culprit. In your WordPress Administration Panel, deactivate all plugins that do not come with WordPress by default. Re-activate them one by one.
Made Custom Changes/Hacks? 
If you have made changes to other WordPress files ("hacked" WordPress), you are supposed to keep track of your changes. You will have to transfer your edits into the new code. WordPress Versions lists the files that have changed in each release.
Resist Using Old Code 
Upgrading gives you the newest and best code. Using your old code, no matter how much you have customised it, almost certainly will cause problems. The temptation just to use your old modified code will be great, but the chances of errors are much greater.
Can I Go Back to Old Versions 
You can, but it is usually not recommended to rollback (revert) your current version to an older version. That is because newer versions often include security updates and a rollback may put your site at risk. Second, the change between the database structure between versions may cause complications in maintaining your site content, posts, comments, and plugins that are dependent upon the information stored in the database. If you are still intent on this, proceed at your own risk. Please note, that without a backup of your entire site and your database, made prior to your upgrade attempt, a successful rollback is near impossible. Delete all WordPress files except for wp-config. Upload the files from your backup to your server and restore your database backup. Remember, you must have good backups for the rollback to work. For older WordPress versions, a rollback might not work.
Get More Help 
If you get any errors following an upgrade, check Troubleshooting: Common Installation Problems, Troubleshooting, and the Codex Installation Category of Articles. If you can't find an answer, post a clear question on the WordPress Suppport Forums. You will be asked if you have used any old code. You'll be told to change it then, so you may as well change it now :)

過去のアップグレード情報

If you are considering upgrading to WordPress Version 5.3, but you are at Version 1.2, then follow the 1.2 to 1.5 upgrade as describe in Upgrading From WordPress Version 1.2 to 1.5. Once you are upgraded to Version 1.5.x, then follow the instructions as listed above to upgrade from 1.5 to 5.3.

最新英語版: WordPress Codex » Upgrading WordPress Extended