WordPress 3.4 Version Released


Update to WordPress 3.4

WordPress 3.4 was released to the public a few days ago. WP 3.4 has been in Beta testing for quite some time, so most bugs should have been discovered and fixed by now – and so they are. The list of known issues is short (Troubleshooting WordPress 3.4 – Master List). More issues have been reported with the latest default theme wordpress 3.4 icon(TwentyEleven) version, and with the JetPack version update released at the same time than with WP 3.4 core.

Should we update our WordPress installations? Generally the answer is yes. It is always a good idea to keep WordPress up to date, however the update should be approached with a degree of caution. Some plugins may not work with the latest version of WP, some themes may also have problems. So before updating let’s consider a few things if the update causes problems, or even worse a broken site.

Before Updating to WordPress 3.4

Prepare to update to the latest version by following a few basic guidelines:

  • Read the release notes and forum posts about 3.4 on WordPress.org and elsewhere.
  • Make sure you have FTP access to your site’s files and folders. Access via FTP is sometimes the only way to get a broken site back up and running again, especially if the WP admin page cannot be accessed.
  • Check the plugins used. This may be a tedious process, but checking what other users have to say about plugin compatibility with 3.4 (or any version) can save a lot of time later. If you find any with known issues with 3.4 deactivate them or consider deleting them completely (or wait for an update that works with WP 3.4)
  • Backup your entire website. This means backing up all the files as well as the database. An offsite backup is essential at this stage. The best way to backup is using FTP to copy the entire site to your computer.
  • If possible, test the site on a local development installation before going live.  (This is a procedure I always use when doing any update to a Drupal system – core as well as every module (plugin), but something I often neglect when updating WordPress).
  • Try to choose a time of day when your site is not busy. This information can usually be found in server activity logs.
  • Set aside time to do the update. Plan on needing several hours or longer just in case something goes wrong. The time probably won’t be needed, but who wants to leave a site offline longer than necessary – bad for Google ranking, bad for visitors too!
  • Let visitors know an update is planned or in progress. Post a status update on Facebook and mention on Twitter (and any other social media.

All Set To Go

After covering these basics, you are ready to update WordPress to the latest version.

me on google plus+Mike Otgaar

About these ads

About Mike

Web Developer and Techno-geek Saltwater fishing nut Blogger

Posted on June 16, 2012, in General News, WordPress and tagged , , , , , . Bookmark the permalink. 1 Comment.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 2,315 other followers

%d bloggers like this: