Due to tests on my WOS ( Webserver on a stick) I can reassure you that WordPress 2.6 (beta-3) and THE MORNING AFTER (1.3.2) are compatible. Id est, there are no limitations in upgrading a plain-vanilla TMA weblog to WP 2.6. You just have to follow these steps:
Before You Get Started
- Just in case something goes wrong, make sure you have a backup. WordPress Backups is a comprehensive guide.
- Make sure the database user name registered to WordPress has permission to create, modify, and delete database tables. If you installed WordPress in the standard way, and nothing has changed since then, you are fine.
- Deactivate your plugins. A plugin might not be compatible with the new version, so it’s nice to check for new versions of them and deactivate any that may cause problems. You can reactivate plugins one-by-one after the upgrade.
Repair the text-based navigation, if enabled
- Unfortunately, the text-based navigation for your the
image.phptemplate that I have proposed in this tutorial is not compatible with WordPress 2.6.
- Therefore, you have to delete this code in your
- Finally, you visit mfields.org and download the plug-in mf_image_links_v1.1. Upload the plug-in to your plug-in folder and activate it after you have finished the upgrading process.
Replace WordPress files
- Get WordPress 2.6. Either download and extract it to your computer or download it directly to the server.
- Delete your old
- Copy the new WordPress files to your server, overwriting old files in the root. You may use FTP or shell commands to do so. Note that this means *all* the files, including all the files in the root directory as well. If you use the default or classic theme and have customized it, then you can skip that theme.
- NOTE! The
wp-contentfolder requires special handling, as do the plugins and themes folders.
- NOTE! Also take care to preserve the content of the wp-config.php file in the root directory. This file contains current settings for your existing installation, e.g. database sign-in information. Beginning with Version 2.6, an AUTH_KEY, a SECURE_AUTH_KEY and a LOGGED_IN_KEY replace the SECRET_KEY for salting (strengthening) user passwords. To improve the chances your user passwords are not ‚hacked‘ here is an example of the line to add to your wp-config.php file:
define('SECURE_AUTH_KEY', 'Zui-S`xfM5NHkj>5VcAEjDA!;3~GoF~v\'X,\'3h?sk5^GL4$. r95tI7< ?yO-K1z^'); define('LOGGED_IN_KEY', 'Z.d#wN/ozZ5Z9VBth}kv5.lp2ExsCVV5;70Q.xH.>],Zz~7nUD3&j\'4a!C#I^ae6');
Upgrade your installation
- Visit your main WordPress admin page at
/wp-admin. You may be asked to login again. If a database upgrade is necessary at this point, WordPress will detect it and give you a link to a URL like
http://example.com/wordpress/wp-admin/upgrade.php.Follow that link and follow the instructions. This will update your database to be compatible with the latest code. If you fail to do this step, your blog might look funny.
- Go to your plug-in admin page and reactivate one plug-in after another.