Designed for hosts with lots of individual WordPress blogs to manage. If all blogs are managed via subversion, this script can iterate through all of them and upgrade each to the latest version in seconds.
WP-Mass-Upgrade has been folded into the WordPress Mass Management Tools kit.
Hi,
Great post, I was actually sent the link by a friend.
I’m interested in setting up a platform for launching hundreds of WP sites that can be mass updated and maintained as your mention here with some other functionality.
Would you be interested in the project or do you know anyone?
Thanks!!
-Jeff
jhenderson419@gmail.com
Hey Jeffrey – Sounds very cool. I don’t have time to get involved, sorry – this script suits my needs very well. Do post here in the future if you end up deploying the project, and let us know how it goes.
Pingback: Links of the day (Dec 13) » Grégory Karékinian
Pingback: IN portal » How to: Installing Multiple Blogs
Hello Scot!
Is there any way to update content on external blogs using your script?
Thanks!
Max – This script has absolutely nothing to do with content – it just manages WP software itself.
Pingback: Upgrading WordPress | WP Queen
Hey Scot if you could add backup that would be awesome… 🙂
Heya – What do you mean by “backup” — what would you want to see backed up? Files or database? Both? Where should they go? When would they be deleted? Just trying to get a sense of what you’re asking for here.
Hi,
does this script update the plugins, too?
And what’s the case with the themes?
Does this script work if my WP blogs are spread across different c-class IPs and nameservers?
Bence – The script does not touch plugins or themes. It doesn’t care about IPs or nameservers – only multiple installations on the same physical server.
Hi,
thanks for the response. Then how can I mass update the plugins and the themes, without logging in to each blog?
I’d think that would be a very dangerous / risky thing to do. Themes are seldom used as-is — they’re usually modified by the user. If the admin were to update them “automatically” he’d likely break things left and right, and piss off users. Plugins generally need to be updated one at a time, depending on its state of development. You’d create nothing but chaos.
In fact, you shouldn’t even be running mass-upgrade until you’ve done a bit of due diligence to make sure you’re not going to break things. I generally wait until the n.1 update of WP is available before running the script, and even then only after checking listings of known-incompatible plugins to make sure none of my users plugins are known to be incompatible with the newest WP release.
But I would like to update my own blogs, not other’s blogs.
Yes, I would update one plugin at a time. Let’s say I have 50 blogs, all of them on different domains, and all the blogs use the XML sitemaps plugin. A new version of that plugin release. I don’t want to login 50 times and click 50 times to update that plugin, how can I do this with command line?
I know there are other solutions (WP Hive, WordPress MU, Virtual Multiblog etc.) but these have limitations. The most robust strategy if I have separate databases and files, right?
Hi Bence – In that case, I would modify the script to deal with such plugins specifically. It would depend on the plugin being available in a subversion repository – all plugins listed in the official WP plugin site should have an svn URL. Just find that URL, modify the script to cd to wp-content/plugins, and do an “svn up” on that plugin’s URL.
Hi everyone – I’m happy to announce a new version of wp-create and wp-mass-upgrade, including automatic backup of each database in the array and a new plugin finding tool. The tools have been folded into a single kit:
WordPress Mass Management Tools