Skip to Content.
Sympa Menu

ibiblio-announce - [ibiblio-announce] WORDPRESS users: upgrade to 3.0

ibiblio-announce AT lists.ibiblio.org

Subject: ibiblio services/changes announcement list

List archive

Chronological Thread  
  • From: Cristóbal Palmer <cmpalmer AT metalab.unc.edu>
  • To: ibiblio-announce AT lists.ibiblio.org
  • Cc: webgroup AT lists.ibiblio.org
  • Subject: [ibiblio-announce] WORDPRESS users: upgrade to 3.0
  • Date: Thu, 17 Jun 2010 18:03:59 -0400

WordPress has a new major release, 3.0.

http://wordpress.org/development/2010/06/thelonious/

If you run a WordPress site at ibiblio, please take the time to
upgrade. We need you to do your upgrade as promptly as possible, and
to help you do that we have a set of instructions for WordPress users
at the following URL:

http://www.ibiblio.org/wordpress/

I'm copying a portion of that page here for your convenience:

Upgrading WordPress on ibiblio

Note that lines starting with a "$" indicate commands issued from
login.ibiblio.org. The "$" is the command prompt and is not part of
the command you would enter. Similarly, items in ALL CAPS definitely
need to be replaced by values that match your site.

1. Use an SSH client to connect to login.ibiblio.org.

2. Back up your database tables. This only takes a minute and can
  really save you some headaches:

$ mysqldump -h MYSQL.ibiblio.org -u MYSQLUSER
--password="SOMEPASSWORD" YOURDBNAME > WORDPRESS-YYYYMMDD.sql

Don't forget to subsitute the values above with yours. For
instance, your database server might be mysql2.ibiblio.org, and
YOURDBNAME will be the name of your mysql database, etc. If you
don't know these values but have a working Wordpress install,
you can find them in your wp-config.php file. Please NOTE that
the backup process will briefly lock the database, making your
site inaccessible. This usually takes less than 30 seconds, but
if you're worried about it, do it during off-peak hours. To save
space, please gzip your SQL backup file:

$ gzip WORDPRESS-YYYYMMDD.sql

3. Disable all plugins. Wordpress upgrades can cause irreversible
damage in some cases if you fail to disable your plugins. You did
make a backup, right?

4. Change directories to the directory above your WordPress installation:

$ cd /public/html/YOURSITE

If your blog is a subdirectory named "wordpress" then you would
do the following:

$ wget http://wordpress.org/latest.tar.gz
$ tar xvfz FILE_JUST_SAVED_BY_WGET
$ rm FILE_JUST_SAVED_BY_WGET

WordPress may want to modify its database tables to accomodate
the new version. Browse to
http://www.ibiblio.org/YOURSITE/wp-admin/upgrade.php and follow
the instructions.

5. If your blog isn't a subdirectory named "wordpress" you'll want
to do something like:

$ mkdir ~/tmp
$ cd ~/tmp
$ wget http://wordpress.org/latest.tar.gz
$ tar xvfz FILE_JUST_SAVED_BY_WGET
$ rm FILE_JUST_SAVED_BY_WGET
$ rsync -av wordpress/ /public/html/YOURSITE/YOURWORDPRESSDIR/

Then proceed to the upgrade itself by browsing to
http://www.ibiblio.org/YOURSITE/YOURWORDPRESSDIR/wp-admin/upgrade.php
and following the instructions.

6. Re-enable your plugins, one by one. If you enable a plugin and
then can't get to your blog, use your SSH/SFTP client to go into
your wp-content/plugins directory, and remove the plugin that
caused things to break. You can simply rename the directory for the
offending plugin and it will be automatically disabled.

That should do it! As always, open a ticket if you have any trouble:

http://www.ibiblio.org/help/

Cheers,
--
Cristóbal Palmer
ibiblio.org
metalab.unc.edu



  • [ibiblio-announce] WORDPRESS users: upgrade to 3.0, Cristóbal Palmer, 06/17/2010

Archive powered by MHonArc 2.6.24.

Top of Page