"SAFE"

感謝 Ivy 當我的 courage booster XD

Wordpress 安全的從 2.0.1 登陸 2.5.1!!!!

自從上次 wordpress 上所顯示的 posts 全部反過來，回到 2003 年 (汗)

於是決定要好好的把 outdated 的 wordpress 給更新

只是遲遲不敢動手 (怕會在一秒之間所有的資料不見 XD)


雖然這次中間過程也沒有那麼順遂 (lots of trial and errors)

不過最後看到熟析的面孔 (webpage) ，終於可以把心放下 T------------T

>>>下個目標 phpbb 3.0~


還有，今天學到新東西了!

原來 ftp 裡面的 wordpress 檔案沒那麼重要

重要的是 database 裡的資料

所有的 post information 都是存在 database 裡~




A great guide I used today: click here

The key to a successful WP upgrade is a healthy database. If the database is stable and has survived the upgrade, and you don’t have any weird calls to obsolete tags in your templates, you are cleared for takeoff. Here are the steps you should follow to ensure that your database (which contains all your posts, pages, settings and comments, your WP site’s heart and soul) survives intact.

1. Backup your database! If you have the WP Backup plugin, just use that to capture the latest MySQL dump. Otherwise, go through your web host’s control panel and PHPAdmin to export the *.sql file to your hard drive.
2. Backup any changed files such as your themes, the quicktags.js file if you’ve customized it, and I usually backup the /plugins folder as well, just so it’s handy and I don’t have to hunt down all the plugins I’ve installed.
3. Disable all your plugins. You can do this manually from within the WordPress dashboard or you can cheat like I do. Just rename your /plugins folder. If WP cannot find the /plugins folder, it thinks you don’t have any installed. You can restore the folder’s correct name after you’ve successfully upgraded.
4. Chart your upgrade path. If you are upgrading from 2.0.11, you should upgrade incrementally, like this: 2.0.11 > 2.1 > 2.2 > 2.3 > 2.5 > 2.5.1
5. Make sure you have downloaded and unzippped to folders all of the WP versions you’ll need to complete your upgrade. You can find them in the download archive.
6. Using your favorite FTP program, upload WordPress, starting with 2.1, from the folder you downloaded and unzipped. DO NOT UPLOAD any .htaccess or wp-config.php files from any of the distros! You will want to retain your own versions of .htaccess and wp-config.php already on your server.
7. Once the first new version is uploaded, point your browser to the /wp-admin folder and upgrade.php. For example, if your WordPress install is at www.yourserver.com, you would go to: http://www.yourserver.com/wp-admin/upgrade.php.
8. Proceed to upgrade the database when prompted.
9. Repeat steps 6, 7, and 8 above (uploading the incremental versions, invoking upgrade.php and updating the database) until you’ve upgraded all the way to WordPress 2.5.1. (Using the upgrade path above, that should be five FTP passes.)
10. After you’ve upgraded to 2.5.1, your WordPress database should be ready to go. Rename your /plugins folder if you cheated in the step above, or login to WordPress and activate your plugins, one by one, testing to make sure your WP site doesn’t throw out any blank pages. If it does, you have a plugin that isn’t ready for 2.5.1. Make a note of it, keep it deactivated (or delete it altogether) and make a note to find a replacement for it later.
11. If you get any kind of errors when working in the backend of WordPress, don’t despair. I’ve saved the best for last. It’s what happened to me. It’s simply a matter of a server burp and a critical file (aren’t all program files critical?) not being uploaded properly during the FTP process. Go back to your FTP program, and delete the following files/folders:
* /wp-admin
* /wp-includes
* all *.php files in the WP root EXCEPT .htacess and wp-config.php
12. Reupload the WP files from the latest version (except any .htaccess or wp-config.php files from the distro). Having deleted the original files, you are ensuring that you have uploaded the freshest versions, not depending on your FTP program to accurately overwrite them.

You should now be able to log into WP and any issues you had should have disappeared. If not, you may want to post in the WordPress Support Forum to find an answer to your problem. Happy upgrading!