dannyman.toldme.com


Excerpts, Technical, WordPress

WordPress Upgraded

I successfully upgraded WordPress to 2.2. I don’t bother with WordPress upgrades that often, because even the simple “Five Step” procedure can get a bit hairy. I’m still grinning at “Step 3: Overwrite Files” . . .

Step 3: Overwrite Files

Get the latest and greatest WordPress and upload it to the WordPress directory, overwriting all the files that exist there only after you have delete the old files, which is explained as follows (do not overwrite your wp-content directory or wp-config.php). Important: when upgrading from 2.0.x to 2.2, or from 2.1.x to 2.2, you will need to delete old files on the server, because several file names have changed. What if something goes wrong, you ask? Well, did you not create a backup of all files in Step 1? You can fall back upon them in the worst case scenario. Deleting your old files on the server and uploading the newer files from the new version you downloaded is an alternative which will ensure that the files on the server have been replaced for sure.

According to my “worklog” file, the process took 25 minutes:

Tue May 29 15:35
- Upgrade WordPress on dannyman.toldme.com ...
- mini:
cd Documents/Backups && make get_ratchet
- ratchet:
/usr/local/bin/mysqldump -u djh --password=?????? djh_wordpress >\\
    $HOME/public_html/toldme/BACKUP/djh_wordpress-2007-05-29.sql
- Disable plugins: Akismet, Customizable Post Listing, Gravatar,
  HeadMeta, Next/Previous Archive Date, Photos Flickr, Related Posts,
  Word Statistics
- ratchet:
rm -rf wp-admin wp-atom.php wp-blog-header.php wp-comments-post.php \\
    wp-commentsrss2.php wp-config-sample.php wp-feed.php wp-includes/ \\
    wp-links-opml.php wp-login.php wp-mail.php wp-pass.php wp-rdf.php \\
    wp-register.php readme.html wp.php xmlrpc.php license.txt
cd ..
wget http://wordpress.org/latest.tar.gz
tar tfvz latest.tar.gz
cp `find wordpress -type f -depth 1` toldme/
cp -rp `find wordpress -type d -depth 1` toldme/
- http://dannyman.toldme.com/wp-admin/upgrade.php ... database upgrade
  done ...
- Per http://codex.wordpress.org/Upgrading_WordPress "Step 5: Reactivate
  Plugins one by one" ...
- Okay, looks alright. :)

Since the documentation is in Wiki format, I suppose I should try to clean it up a bit . . . try not to get too smarmy:

Step 3: Overwrite Files

Get the latest and greatest WordPress and upload it to the WordPress directory, overwriting all the files that exist there.

Important: If you are upgrading to WordPress 2.2 from 2.0.x or 2.1.x then someone who wrote a previous version of this page thinks it important for you to delete any WordPress filenames that may have changed. Take a look at the Delete the old WordPress files section for clarification.

“What if something goes wrong,” you ask? Well, did you not create a backup of all files in Step 1? You can fall back upon them in the worst case scenario. Deleting your old files on the server and uploading the newer files from the new version you downloaded is an alternative which will ensure that the files on the server have been replaced for sure.

Read More

Next:
Previous:
Categories: Excerpts, Technical, WordPress

  • Ben

    I’m a slacker Dreamhost user – I just used the “one click install/upgrade”. Didn’t need to do anything special to migrate plugins. Just hit the button, wait for the “we’re done” e-mail in 5-10 minutes, and hit /wp-admin/ to update the DB.

    The “basic” answer is to put everything you might customize (plugins, under your wp-content/ folder. Last time I upgraded a version at the command line, it was just:

    $ tar xvzf wordpress-latest.tar.gz
    $ cp -a blog/wp-content/ wordpress/wp-content
    $ cp blog/wp-config.php wordpress/wp-config.php
    $ mv blog ~/not_public_html/blog_old
    $ mv wordpress blog

    Then, visit the admin pages to run any upgrades. Done and done. I think the WP.org folks write their documentation assuming that the average WP user doesn’t have shell access.