Matt wrote, “Today we have two security-related releases available for both users of our main 2.2 branch and the legacy 2.0 branch. As these releases include only security and minor bugfixes they should not cause any plugin or theme compatibility issues, so you have no good excuse not to upgrade.
The biggest problem I have with WordPress is upgrading.
1) I can’t trust an upgrade will work so I dare not upgrade because I don’t want my blog going down. Upgrades need to be bulletproof.
2) The actual upgrade process is a pain in the buttocks. Bad enough for a single deployment but I must do it for my two blogs plus both of my sons, my wife, etc. I would like to just do it once for all of them. Doing each one separately takes a lot of time.
3) I’ve got blog posts and a life. Thus upgrading gets stuck in my “Round-Tu-It” draw, something I’ll do when I get around to it. Then another upgrade comes out…
4) Many software packages upgrade themselves – with the permission (check box) of the user. This would be far better. It notices the upgrade, and does it, at most asking. This still doesn’t solve #1 above but it does solve #2 and #3.
5) Upgrading should automatically first create a backup zip file of the database and all associated files before even thinking about touching the system. Basic IT.
So, once again, I might not upgrade and yes, I do have excuses.
- The topic ‘Upgrading is a bother’ is closed to new replies.