WordPress 4.1.1 Released
WordPress 4.1.1 was released today. This is a minor (0.0.1) update, providing bugfixes for the 4.1 release.
What’s New
This release fixes some minor problems with 4.1 – 21 bugs were fixed, but it’s likely you won’t notice any changes to your WP install.
Upgrading to WP 4.1.1
Some users like to wait for the first minor release after big changes before they update their sites. Historically that has been a good idea at times, as major updates can introduce larger problems, which are then resolved in the first minor update. But 4.1 seems to have been relatively trouble free for the vast majority of users. With this release, it is probably time to move up from the 4.0.x series. For anyone already running 4.1, there is very little reason not to update. As usual, this post is being written on the most current version.
Our Upgrade Process
If you have turned on automatic core updates for minor releases, then a backup will be taken of your site, followed by an automatic update. Note that it is now possible to disable this backup if you don’t have space in your account, and rely on our nightly backups instead. This is rolling out across the servers as I write, and will be applied to all sites within the next 24 hours.
Problems?
There is always the potential for a problem post-update. If that happens, remember that we have automatic backups taken offsite nightly, which can be restored via the ‘Bacula4’ icon in cPanel. If you need any assistance, don’t hesitate to open a ticket in our client area and we can help. It’s usually best to check the ‘error_log’ file in your site’s root directory to see if there are any problems listed there, then run a restore. The error_log files content describes PHP errors and may help you determine what went wrong, and we can then help determine how to get your site upgraded to 4.1.1.
