WordPress 3.4 was just released to the public Wednesday, June 13, 2012.
This major release includes significant improvements including theme customization, custom headers, Twitter embeds, and image captions.
Highlights of WordPress 3.4 Video:
You can find out more about the new features of 3.4 at the WordPress codex, or read all the WordPress 3.4 news at WordPress.org.
There is a Troubleshooting WordPress 3.4 – Master List over at the WordPress forums that you should check out too.
To enhance your WordPress security, we recommend you upgrade to version 3.4 as soon as possible.
Important! Before upgrading be sure to do the following:
- Backup your website (both database and files). I recommend using BackupBuddy
- Check your plugins and theme to make sure they're compatible
Note: The best thing to do is to copy your site in a testing environment and try the upgrade there. Not sure how? Create a sub-directory on your hosting account and use the BackupBuddy “ImportBuddy” feature. Remember to delete your test site afterwards, you don't want an abandoned WP site on your server that you will most likely forget to update.
What to do if your plugin or theme is not compatible? Contact the developer and ask them for an update that supports WordPress 3.4 or find a replacement. For best WordPress security practices, you always want to have the latest version of WordPress running on all your sites.
If you need help, contact us.
I can't wait to dive in and check out all the new features and WordPress security enhancements too. How about you?
LEAVE YOUR FEEDBACK
Let us know how your upgrade to WordPress 3.4 went. What's your favorite new feature? Notice any plugin conflicts? Leave your comment below.
Securely yours,
Regina Smola
WordPress Security Expert
Follow WPSecurityLock on Twitter
Become a Facebook Fan
I just updated my WordPress and I ended up on an error page because I had DB cache reloaded active. Folks if you have DB cache reloaded installed, first disable it before updating.
Hi Sreejesh,
Thanks for letting us know!
Did you install on WordPress 3.4 manually (via FTP) or from the Dashboard? And did you upgrade on a test or live site? What did you do to get your site back after you got the error page?
I’m sure your feedback will help many others.
Thanks Sreejesh!
I found mention of the DB cache plugin causing issues on the Troubleshooting WordPress 3.4 – Master List.
Thanks, Regina… appreciate the Back Up buddy instructions… plus new V of BB just came out today, also! So, alot to absorb and make sure all is done correctly.
Off topic… what plug in do you use on your blog here for the share feature?
Hi Christine,
You’re welcome. I have upgraded and testing the new version of BackupBuddy and it worked perfect! I just wrote a blog post about it too https://wpsecuritylock.com/wordpress-security-backupbuddy-3-0/.
I am using the SexyBookmarks plugin. But I think I’m going to hardcode it in my theme in the near future. For me, the less plugins the better 🙂
FYI: https://wpsecuritylock.com has been successfully upgraded to WordPress version 3.4. No hiccups and running smooth 🙂
Regina…glad to hear, as I was a little hesitant after a big rant on FB from an acquaintance about NOT upgrading yet, and that it broke his site.
I have minimum amt. of plugins on the sites, and will do full backups first. One of the themes is a bit outdated, so a little concern there. But let’s cross our fingers. 🙂