WordPress versions Out of Control
August 22, 2007
I’m a HUGE fan of WordPress as both a blogging platform and (to some extent) a CMS for websites. But there is one thing that threatens my support:
Too many version changes.
Lately WordPress has been changing versions literally once a month. Here are some cliches for the folks behind WP…
Less is more.
There is a reason why it’s not Windows Monday, Tuesday, Wednesday…etc (OK-bad example. They have updates-grin)
It takes a really good change to beat no change at all.
Measure twice. Cut once.
Is the reasoning behind the change SO critical that it must be rushed out?
Etc.Etc. Etc.
It takes an immense amount of time to upgrade blogs with each version change. This is true even for the most prolific and seasoned of us. So as a favor to those of us loyal users out there, can we PLEASE keep “stable release” from being something besides and oxymoron?
Thoughts?
Hmm….
First of all, nobody actually forces you to upgrade to every version. You can skip updates once in a while, especially if the update is not critical.
Secondly, which part of the update does take you “an immense amount of time to upgrade”? WordPress is well known for its 5-minute install. The upgrades are even faster – simply copy the file over and you are done.
With WordPress being an open source software it is trivial to see which parts were changed between versions. You can choose if you want those changes. You can upload just the changes to your server, if the whole archive takes too long.
Heck, I am using my own version of WordPress, and it still takes me no time at all to merge changes between WordPress versions with my own changes…
Leonid;
Good to meet you! I paid a visit to your blog. Very enjoyable read.
Since I manage and host about 30 blogs, every time an upgrade appears, i get someone asking me “why aren’t we at version 2.latest?” (grin)
You are totally correct about a skip here and there on my own blogs…I am happy to skip it until a really important change is made.
Another issue is that I use plugins for some of the blogs that get all borked up when doing an upgrade. Then you have to go back and source the problem and correct the code. All time consuming.
That having been said, your points are well taken AND WP is the best platform by far out there in my opinion.
So being from Cypress, where did you find my blog?
Best regards
Eric
Eric,
Automation is the key, if you have a lot of blogs going on. Even testing can be partially automated (no PHP or MySQL errors appear on a page, but control strings (like “Copyright” appear, and things like that).
Alternatively, you might want to take a look at WordPress MU ( http://mu.wordpress.org ). It’s designed for multiblog installations. Even the regular wordpress.org version can be used in a single instance for multiple web sites though some wp-config.php trickery.
If maintenance kills you, spend some time looking at those options. There is probably a better way to do things.
P.S.: I found your blog post through a random search fro WordPress at Google BlogSearch.
Cheers.
Unless there’s a good reason to make the change, I usually stick with what I got. Sometimes, “updates” can cause more problems than what they are trying to fix in the first place.
Leonid,
I have to agree with Eric, it is time consuming. I wish it were as easy as you make it sound. And the way you describe is like playing russian roulette with your blog.
The 5 minute install is the first time. The upgrade process in 5 minutes. I don’t thinks so.
Back up your database files
Deactivate all your plugins
Copy the upgrade files to the server
Run the upgrade script
One at a time activate the plugins. Testing after each activation to be sure nothing has changes.
Then find out what still works and what they broke with this upgrade which sometimes includes things as critical as wiping out the permalink structure on your blog. (which one upgrade did) making your blog disappear.
Again, I’m with Eric, fewer upgrades and better testing before a new release. I find new things broken almost every release. It also drives plugin and widget creators nuts because they can’t keep up with the changes so such basic file structures as how comments are handled.
@Leonid–I actually have tried MU on an autism related site…is there a good way to handle the splogs besides just deleting them every day or so?? I have not had a chance to get back there to upgrade that / find a fix for that problem…
Thanks for letting me know how you found me! Hope all’s well for you there!
@Dave-Yep. I love the WP guys for what they’ve created, but I am hoping for less updates in my Christmas stocking this year! (Notice that I blogrolled your blog lab–) Thanks for creating a good solid resource for REALTORS who are blogging.
Dave,
I see now… the way I do the upgrade is way simpler.
1. No need to backup database, as it is a part of routine daily backup. Skip.
2. Deactivate all plugins. I don’t do it. There is no need, as plugins aren’t getting upgraded themselves.
3. Copy the upgrade files to the server. No way to avoid this. But there are ways to speed it up. If you do a full upload over FTP, it might take a while, since there are plenty of small files. Alternatively you can either upload only the changed files (the list is often published with release notes or on support forums or can be easily established with diff/SVN). Or you can upload the tar.gz/zip archive to the server and unpack it there, if you have shell access. Time saver.
4. Run the upgrade script. Usually takes about two seconds.
5. One plugin at a time? No way! That’s why I don’t deactivate them in the first place. If something is broken, something is broken. If not – then not.
6. Troubleshooting issues is much simpler if you have access to the log file or display errors on the main page. Problems are usually easier to localize if you spot the area where they happen – RSS feeds, comments, sidebar, search, etc.
If you run a very important and highly popular web site, than you might want to have a test platform – a replica of your web site with all data (daily dump is fine) and plugins and theme. Then try to upgrade it and see if you have any problems.
Also, if you are worried about the upgrade, give it a day or two – most serious problems will be spotted by other people and reported both in Trac and on the support forums.
Eric,
there are a few anti-spam plugins out there, ranging from blacklist to captchas. My experience in this area is rather limited, so I don’t have any particular solution for you.
Eric,
Yes, I notice the inclusion in the blogroll, you put me with some pretty hefty company. I’ll try and keep the lab up to snuff.
BTW, I’m an old sort of sod, when I come to your blog, is there a way to find the posts without clicking on the archieves?
@Leonid–thanks for the insight. I think my biggest worry with that is the plugins. Dave has actually had plugins strip off tags and have to re-create them…The problems that a broken plugin can create can be a pain to test. It is interesting to see your method, though. Thanks.
@Dave-you’re not in hefty company. You are in your rightful place on this blog at least.
As for the posts…I am doing some re-org of the blog tonight to change some things around. Instead of sticking page 1 as its own page, I am likely going to stick an intro post to the top of page one with posts below. Been mulling that one over awhile myself…Just haven’t found the style I like yet. FTR–I AM going to add some graphics though…just haven’t had time.
Check in tomorrow and let me know what you think!
Leonid,
Deactivating plugins and activating them one at a time is straight out of the WordPress upgrade docs. Of course you can skip those steps but it is a gamble. I’ve had quite a few plugins blow up a blog when reactivated and had to go in a back door and turn them off.
All this being said, “I still love WordPress.”
Eric,
Even adding the Recent Posts to the sidebar near the top would do the trick. I’m assuming you are running widgets.
For those cases when upgrade actually breaks something, there is a full backup, no?
You can restore your site back to its original state and, once you know that there are problems, you can solve them on a slower pace somewhere else – again, using the support forums of WordPress and reporting bugs to plugin authors.
I also have to agree with Eric, it is time consuming. Too many version changes is not a good thing. I don’t change myself unless there is a real reason to do so. Thank