Sorry - started to reply and then lost net access for a couple of days. If it isn't too late, here's some info that may be of use
- Brian Layman's EasyWPUpdate does just what you describe and he recently reported on his blog that he upgraded 8 sites to WP2.7 in 30 seconds.
- I searched google on shell script to update multiple wordpress installations and found some others that looked promising, in particular the one by David Tucker.
- check out the WP Codex on installing multiple WP blogs via shell scripting [codex.wordpress.org]. That might help.
- Using Subversion to maintain WP [codex.wordpress.org] might be a long-term solution. Haven't tried it with WP. I've had good luck with some other packages, less good luck with others.
- I've recently experimented successfully with using sym links and some scripting in the wp-config file to run multiple blogs off the same code base, so you only upgrade once anyway.
When there is a major WP upgrade, there are usually some changes to the DB and you must run the DB upgrade script for every site. I don't know of any method that gets you out of this duty except, of course, actually hosting your blog on Wordpress.com (though on your own domain of course).
So if there are DB changes, you'll have to open every site individually as an admin and run the update script.
SVN is the ultimate way to maintain any php program install.
But rushing to upgrade is crazy as any plugins you depend on might break instantly and you can't roll back database changes unless you backed up.
Wait for 2.7.1 - always happens a week or two later.
>>Wait for 2.7.1 - always happens a week or two later.
I always wait unless there's a critical security issue. For a major upgrade, I do a search for app-name version-num plugin-name for each installed plugin/module
I was composing a longish post with a few images and links and when I went to save, I got the dreaded login screen. I lost most of the content and my rewritten post was much shorter.
My guess is that I had not noticed that the ADSL link had dropped but had later resumed, so I was technically logged out when I tried to post. I don't know if WP made numerous attempts to save the post like it should while I was writing it, but I didn't get any error notification.
So, for the time being I will save manually as often as I can remember.
>>ADSL link had dropped but had later resumed
I wonder why that happened. Is WP storing the IP in the session data and checking that the current IP is the same as the login IP (and you're generating new dynamic IPs every time you get a connection)? Because of my situation, I'm often dropping connections and reconnecting and as long as I don't delete the session cookie, I stay logged in.
Also, at least for 2.6, WP is set to save posts as drafts every minute. So I can't actually lose more than that. I suppose that depends on allowing an xmlrpc connection, which presents its own risks and which, I believe, WP now has off by default.
Personally, I usually write long posts in Notepad++ or Dreamweaver and then paste them into WP.
Just to add to whats been said. WordPress 2.7 is supposed to now have an automatic upgrade function built in so this "should" be a problem of the past. Only time will tell. Honestly automatic upgrades make me nervous and I usually disable them.
Have you looked at WordPress MU? It has the ability to host many blogs on one codebase so you only have to upgrade once. It also tends to lag the upgrade sequence of WP which I like because then I know the problems with WP have usually been fixed before the equivalent upgrade of WP MU comes out.
Also the numerous updates to WP should slow down now they have fixed the admin interface. I have an e-book on WP and WP MU and am so tired of having to go back and revise it with every update so this was welcome news if true.
I haven't looked at WordpressMU in ages, but it seemed last I looked that it was not compatible at that time with the plugins I wanted or with regular WP themes. Is that correct?
wow thanks - bryans thing looks sketchy not sure if I am looking a the right blog.
just played with WPMU - its weird and I gave up =P will wait for 2.7.1 i guess. but man I have too many sites using WP as a CMS - just need a simple upgrade button :)
I havent paid attention to this thread in a while. Yes, there are certain plugins and themes that are not WP MU compatible though I am finding less and less. WP MU is less intuitive at first than plain old WP but once the initial learning is done, its a breeze.
If you have installed WP 2.7, then go to Tools and under there you will see Upgrade. This is supposed to be a one click upgrade for WP. Since there havent been any releases since 2.7, I havent seen it in action yet. WP MU 2.7 should be out end of Jan or early Feb by current estimations though not sure yet if one click upgrade will be incorporated.
Thanks for the info reprint. I haven't looked into in such a long time and last time I looked it was on a whole different major version number (like WP was at 2.3 or something and WPMU was at 1.x). I was never sure if there was any effort to keep them at all in synch, but it sounds like the answer is yes.
I'll have to give it another look.
By the way, by using symlinks you can easily run multiple sites off one WP code base. The only hassle is upgrading the DBs manually. I think that's for another thread though.
They are semi in synch. WP MU lags behind WP because Donnacha gets lumped with most of the work whereas for WP the workload is spread out more.
It fulfills a need for me for relatively small sites that are related to each other. I keep them logically organized because if and when it comes time to sell, it is easier to sell the package as opposed to picking individual unrelated domains out of MU and dumping them into WP for purposes of sale.
I heard of the other solution, ergophobe but never gave it a go.
See what you think of MU now. I would be interested to hear your opinion.