WordPress 3.5.1 was released to the public on January 24, 2013. Within WordPress 3.5.1 there are several maintenance upgrades wrapped in a minor security release for all previous versions.
This release addresses issues with the post text editor, the media manager, network rewrite rules upon new network creation, scheduled post glitches, problems with the wp-admin area's scripts, some plugin error messages, and more. Be sure to check out the list at Codex Version 3.5.1.
Upgrading to WordPress version 3.5.1
A word of caution before you update! As with any WordPress upgrade, certain plugins or themes could break your WordPress site. Before you push the “Please update now” link, be sure you have a full backup of all your site files and database.
One of my favorite tools for backing up WordPress is the *BackupBuddy plugin.
The link above is my affiliate link. Save 25% off your order with coupon code WPSECURITYLOCKS.
People ask me all the time, “Is it safe to upgrade WordPress now?” The answer is simple. If you are not using a plugin or theme that will conflict with WordPress 3.5.1 then you should be fine. Check your plugins and theme to see if they are compatible. Copy your site over to a test environment and try the upgrade there first. You certainly don't want to break your “live” site. (If you need help, contact me.)
Very Helpful Links:
- WordPress News: WordPress 3.5.1 < Official Press Release
- WordPress Codex: Version 3.5.1 < Summary of highlights and features
- WordPress Codex: Using Your Browser to Diagnose JavaScript Errors
- WordPress Trac: Milestone 3.5.1 < Tickets active and closed
- WordPress Codex: Changelog/3.5.1 < This should be updated soon
- Download WordPress 3.5.1
- WordPress Codex: Upgrading WordPress Extended < Our preferred upgrade method
Please share your experience with upgrading to WordPress 3.5.1. Did everything go okay? If you find a plugin or theme with issues, let us know. Got questions about the WordPress security fixes? Leave your comment below.
Ranjan says
Hi Michael,
Good information and ofcourse great question”Is it safe to upgrade WordPress now?” But I never install or update the recent release rather than before applying on the dummy site. Because there are catching eyes also watch the updates and in search of vaults.
By the way Thanks for sharing
Michael Schultz says
Thanks for your feedback, Ranjan! You’re right. It is definitely wiser to have a copy of your site on a sandbox elsewhere that you can run things on first to ensure that you and your visitors don’t experience any downtime.
Shane Curtis says
Thanks a lot for the review.
It is indeed help us to have more effective kind of security and this is definitely good.
Gurwinder says
I had upgraded and it working fine for me.
Keith Davis says
I always deactivate all plugins before an upgrade and reactivate after upgrade.
Just have to remember to reactivate them.
I use the BackWPup plugin for database and site files backup.
With that plugin you can backup to Dropbox.
Just upgraded all my local and live sites – no problems.
Ian Said says
You talk about ‘copying your site over to a test environment’. How does that work? What is a test environment? Thanks for all the great security tips.
Thanks,
Ian
Ejiro Idolor says
A theme I was using on one of my blogs that wasn’t working with WordPress 3.5 worked perfectly with WordPress 3.5.1
I updated all my blogs 24 hours after the update came out…. unluckily a friend of mine was hacked.. Why? He forgot to update his blog as he thought it was the job of his webhost
Regina Smola says
Hi Ejiro,
It’s amazing at how many people think that the webhost is responsible for keeping their site content/systems up to date. Thanks for pointing that out again.