WordPress.org

Ready to get started?Download WordPress

Codex

Обновление WordPress (подробно)

Эта страница помечена как незавершённая. Вы можете помочь проекту, дополнив её.

Contents

Подробные инструкции

Обзор процесса обновления

  1. Сделайте резервную копию базы данных. Подробности можно найти в статье «Создание резервной копии базы данных».
  2. Сделайте резервную копию ВСЕХ файлов в каталоге WordPress. Помните о файле .htaccess.
  3. Проверьте резервные копии — убедитесь, что ими можно воспользоваться. Это важно.
  4. Деактивируйте ВСЕ плагины.
  5. Убедитесь, что первые четыре шага выполнены. Не предпринимайте обновление до выполнения этих шагов.
  6. Скачайте и разархивируйте дистрибутив WordPress с http://ru.wordpress.org/releases/.
  7. Удалите старые файлы WordPress с вашего сайта, но НЕ УДАЛЯЙТЕ:
    • файл wp-config.php;
    • каталог wp-content; Исключение: каталоги wp-content/cache и wp-content/plugins/widgets можно удалить.
    • каталог wp-images;
    • файл .htaccess — если вы добавляли собственные правила в .htaccess, не удаляйте его;
    • файл robots.txt — если ваш блог расположен в корневом каталоге сайта (т.е. блог и является сайтом), и вы создали этот файл, не удаляйте его.
  8. Загрузите новые файлы с вашего компьютера в соответствующий каталог WordPress на сайте.
  9. Запустите процедуру обновления WordPress и следуйте указаниям на экране.
  10. Обновите постоянные ссылки и .htaccess. Обновите структуру постоянных ссылок и созданные вами правила (если есть) в файле .htaccess.
  11. Установите обновлённые плагины и темы. Посмотрите список плагинов, работающих с версией 3.8.3. Проверьте совместимость вашей темы с версией 3.8.3 и спросите у автора темы, доступна ли новая версия.
  12. Повторно активируйте плагины
  13. Добавьте ключи безопасности в файл wp-config.php
  14. Посмотрите, что изменилось в WordPress.

Это краткий обзор процесса обновления. Подробные инструкции вы найдёте ниже.

В случае возникновения проблем повторно прочтите приведённые ниже инструкции, чтобы убедиться в правильности всех действий, и обратитесь к разделу «Решение проблем: Основные проблемы при установке».

Обновление с версии 2.7.x до 3.8.3

Выполните шаги 1-4, затем посетите Administration > Tools > Upgrade и нажмите кнопку "Обновить автоматически".

Detailed Upgrade Instructions for 1.5.x, and versions 2.0 - 2.6.5, to 3.8.3

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

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.

Step 2: Back up ALL your WordPress files

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.

Step 3: Verify the backups

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. Also consider opening a .sql file in an editor to see if the tables and data are represented.

Step 4: Deactivate ALL your Plugins

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

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.

Step 6: Download and extract the WordPress package

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-3.8.3.tar.gz | tar -xf - or by using: tar -xzvf latest.tar.gz

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

Step 7: Delete the old WordPress files

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--only older installations from 1.5.x days will have this folder;
  • wp-includes/languages/ folder--if you are using a language file, and it is here rather than in wp-content/languages/, do not delete this folder (you might want to move your language files to wp-content/languages/ for easier upgrading in the future);.
  • .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. Note: some files such as wp.php may not exist in later versions such as 2.7.
  • wp-admin folder;
  • wp-includes folder; If you have a language file here, remember not to 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.

Step 8: Upload the new files

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.

Step 9: Run the WordPress upgrade program

Using a web browser, go to the WordPress admin pages at the normal /wp-admin location. WordPress will check to see if a database upgrade is necessary, and if it is, it will give you a new link to follow.

This link will lead you to run the WordPress upgrade script by accessing wp-admin/upgrade.php. Follow the instructions presented on your screen.

Note: Make sure the database user name registered to WordPress has permission to create, modify, and delete database tables before you do this step. If you installed WordPress in the standard way, and nothing has changed since then, you are fine.

If you want to run the upgrade script manually:

  • 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

If you experience difficulties with login after your upgrade, it is worth clearing your browser's cookies.

Step 10: Update Permalinks and .htaccess

In your Administration > Settings > 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.

Step 11: Install updated Plugins and Themes

Please review the Plugin Compatibility List and Theme Compatibility List, or plugin/theme authors, to find plugins and themes compatible with your new WordPress version. Upload and install new versions of your Plugins and Themes, if necessary.

Step 12: Reactivate Plugins

Use your Administration Panel, Plugins, to activate your Plugins. If your plugins do not appear on the Plugin Compatibility List and you are not sure if they will work correctly with the new version, activate each plugin, one at a time, and test that there are no problems before continuing.

Step 13: Add security key definitions to the wp-config.php file

Beginning with WordPress Version 2.6, three (3) security keys, AUTH_KEY, SECURE_AUTH_KEY, and LOGGED_IN_KEY, are used to insure better encryption of information stored in the user's cookies. Beginning with Version 2.7 a fourth key, NONCE_KEY, was added to this group.

If you don't find the keys in your wp-config.php file, add the keys definitions with reference to Editing wp-config.php - Security Keys, and upload to your server.

Step 14: Review what has changed in 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 3.8.3. A detailed explanation about DB_CHARSET and DB_COLLATE can be found in Editing wp-config.php.


Other languages

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.5 to 2.0.6, 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 fino alla 2.7, dalla 2.7
Korean 1.5.x, 2.0.x to 2.1, 2.0.4 to 2.0.5
Spain, Castellano 2.2 to 2.2.1, 2.2.1 to 2.2.2, 2.2.2 to 2.2.3, 2.3 to 2.3.1, 2.3.1 to 2.3.2, 2.3.2 to 2.3.3, 2.3 to 2.5
Thai, ภาษาไทย การอัปเกรดเวิร์ดเพรส
Vietnamese, Việt 2.5 to 2.6
Turkish, Türkçe none specified
Russian, Русский old to new
Ukrainian, украї́нська мо́ва any 2.0.x to 2.3.x, 2.0.5 to 2.0.6

Проблемы и решения

Повредилась разметка или появились ошибки 
Если ваш блог выглядит поврежденным или выдает ошибки, в этом могут быть виноваты старые плагины, которые не работают с обновленным кодом. В Консоли администратора деактивируйте все плагины, которые не идут в комплекте с WordPress, и повторной активируйте их.
Вносили изменения/хаки? 
Если вы вносили изменения в файлы самого WordPress ("ломали" его), отслеживайте ваши изменения. Вам потребуется внести ваши правки в обновленный код. Здесь список измененных файлов для каждой версии.
Избегайте пользоваться старым кодом 
Обновление дает вам самый новый и самый лучший код. Использование устаревшего кода, вне зависимости от того, как хорошо вы его отлаживали, всегда является возможной причиной сбоев. Искушение использовать исправленный старый код будет велико, но так же увеличится шанс появления ошибок.
Могу ли я вернуться к старой версии 
Да, вы можете, но обычно это не рекомендуется. Во-первых, новые версии включают в себя обновления безопасности и откат подвергнет ваш сайт риску. Во-вторых, изменения в структуре базы данных между версиями могут повредить целостность контента, записей, комментариев и настроек плагинов, сохраненных в базе. Если вы все еще хотите это сделать, то вы делаете это на свой риск. Пожалуйста, имейте в виду, чтобы без резервной копии всего сайта и базы данных, сделанных ПЕРЕД обновлением, успешный откат почти невозможен. Удалите все файлы WordPress кроме wp-config. Загрузите файлы из вашей резервной копии на сервер и восстановите из резервной копии базу данных. Помните, у вам должны быть рабочие резервные копии для того, чтобы откат был успешен. Для старых версий WordPress откат может не работать.
Получите дополнительную помощь 
При получении любой ошибки по время обновления, обратитесь к разделу Проблемы и решения: Общие проблемы установки, Решение проблем, и статьям из рубрики Установка. Если вы не можете найти ответ, задайте вопрос на Форумах поддержки WordPress. Вас спросят, использовали ли вы устаревший код и расскажут, как его надо изменить, чтобы вы могли сами исправить вашу ситуацию :)

Old Upgrade Information

If you are considering upgrading to WordPress Version 3.8.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 3.8.3.