Upgrade Your Stage: WordPress 3.3 Released

Wooden stork with "baby" package in its mouthCongratulations — it’s an upgrade!

WordPress 3.3 was released this month, and now the question is: is it time to upgrade your WordPress site? The answer is a  mostly unqualified “yes.”

New Features in WordPress 3.3 – aka “Sonny”

WordPress 3.3 adds several new features to the administrative interface — the “Dashboard” — that make life a lot easier, particularly for mobile users. Previous iterations never really scaled on the smaller screens of the iPhone or other smart phones, but this one is supposed to render quite nicely on the smaller display.

Some other key features that I like:

  • Drag and drop uploader for all kinds of files — images, PDFs, what-have-you
  • Much cleaner file uploading and management process generally, with a single upload button for every file type
  • Revised navigation menus with hover expansion — makes it much easier to find what you’re looking for
  • Improved co-author controls — that “Warning: [user name] is editing this post” thing only pops up now when someone is actually actively revising the post at that time.
  • New Toolbar in the Dashboard combines the admin bar and the admin header into one sleeker strip at the top of the browser display, freeing up real estate and making the whole UI much cleaner in appearance
  • Widgets make the journey when you change themes now — very convenient
  • Fly-out menus on the sidebar menu in the Dashboard, which is a vast improvement over the drop-down approach we’ve been used to

You can see a full list of the features in the new release here.

Protect Your WordPress Site From Hackers

Of course, the first thing you need to do before you use the built-in automatic WP updater (which, I confess, is so convenient and so much easier than the old by-hand/”scratch” method, although some folks have reported problems with it), is to back up your site thoroughly. Here’s a great post from Kim Castleberry at Just Ask Kim on how to do the backup thing correctly.

Even so, you might want to take some extra precautions. WordPress is a great platform but it’s susceptible to hackers just like any site, and maybe even more so, when you factor in how easy the platform makes website management. Even rank beginners with no coding experience whatsoever can handle a WP site — which is great, don’t get me wrong. But the flip side of that is that a website owner can be lulled into a false sense of security by WP’s ease of use, and neglect to protect the site from unwelcome intrusions.

Tea Silvestre at The Word Chef shares her hacking & WordPress security story here; some of the resources she links to there are the very ones I’d recommend, particularly the WP Security Scan and Secure WordPress plugins. I’d also highly recommend this piece from Adam Warner of WPPro Business, which Tea links to in her piece, that covers security management and database naming, and this follow-up piece Adam did about the WP Security Scan plugin.

Checking Your Plugins Before Upgrading to WordPress 3.3

I can’t overstress the importance of checking your plugins’ compatibility with WP 3.3 before upgrading. A plugin that doesn’t play nicely with the new version can quite easily bring your site to its knees in no time flat.

The best way to do this is bring up your list of active plugins in your WP Dashboard, and click on the “plugin site” link for each. Alternatively, go to the WordPress Plugin directory and search for each one. Check the “Compatible up to” data on the right-hand side under the big “Download” link. If it’s at least updated through WP 3.2, you should be OK. If not, then disable the plugin before upgrading.

When Should You Upgrade?

It’s not a silly question. Do it too early and you might be at the mercy of bugs that haven’t been identified and corrected yet. But by the same token, there’s such a thing as waiting too late to upgrade, too. Don’t delay upgrading too long. It leaves your site open to potential hacking invasions and corruptions.

Give it a week or so after a major release, to give the WP developer community time to suss out needed tweaks and make them. Then, back up your site, and hop to it!

{ 6 comments… read them below or add one }

CAELAN HUNTRESS December 18, 2011 at 1:26 am

Great overview, Annie! I wish they AutoMattically gave us a synopsis as good as this with the ubiquitous ‘Upgrade NOW!’ links I see in all my WP dashboards.

Adam W. Warner December 18, 2011 at 3:22 am

Hi Annie, thanks for the mention, it’s most appreciated:) Regarding checking plugins…I did encounter one plugin issue when upgrading that other people have had trouble with too…it was (IS) the Popup Domination plugin. Unfortunately I haven’t seen any word from them regarding a fix yet, so it is still deactivated.

It’s probably a bit of Karma as I was thinking of axeing that plugin anyway…I paid a decent price, but there latest version update is mostly cosmetic and even previous buyers need to purchase again (at a discounted rate), and to be fair there are a couple of feature enhancements but these can be found in other popup plugins. As you can tell I’m soured;)

Anyway, thanks for the link love and if you’re interested, I have a new WordPress Security manual releasing soon that you may be interested in. If so, please shoot me an email and I’ll put you on the short list for a review copy:)

Annie Sisk January 2, 2012 at 11:15 pm

Hey thanks, Adam! Will be in touch. There are also some noises about Contact Form 7 that are concerning (that’s what I use though I haven’t found a problem yet).  Plugins can make life SO much easier, but also so much more complicated post-upgrade! 

Annie Sisk January 2, 2012 at 11:15 pm

Aw, thanks, Caelan! I appreciate the kind words. 🙂 

Lasandrahutchinson January 11, 2012 at 8:57 pm

You know, I need to bring over everything from my blogger blog to wordpress. Any idea?

Annie Sisk February 19, 2012 at 7:46 pm

Sheesh. Thanks, Disqus – Lasandra, I just saw your comment TODAY. Depending on a few parameters, yeah, you should be able to import from Blogger into WordPress just fine. See here: http://codex.wordpress.org/Importing_Content#Blogger

Leave a Comment

Previous post:

Next post: