will your 20+ sites require similar plugins?

the problem i ran into managing multiple sites from a single install is that plugin compatibility becomes an issue.

if you’ve got 20 sites using 25 different plugins, there’s a good chance some of those plugins won’t be supported in the next release of WP. when that happens, you’re forced to either use an older version of WP or look for a newer plugin.

it becomes a pain, honestly. making sure upgrading WP won’t break any existing plugins or vice versa.

that’s why i’ve found it easier to maintain separate installations. now that WP has made the upgrade process simplier, it’s become less of a hassle for me to do this.

Although now that I have more experience managing multiple WP blogs serving different purposes, I’m learning more towards separate installs.

One installation is good if the sites serve similar purposes and have common functionality. The blogs/sites I manage are very different across the board.

As an update to this post, I’ve actually switched all of my sites back to VMB.

A couple reasons.

1. Lack of development. The developer keeps promising updates, but there has been very minimal movement in the past year. I’ve pretty much resolved WP-Hive is not going to ever evolve past its current point.

2. According to the WP-Hive blog, it looks like the project will be moving to the freemium model.

A very basic feature I’m looking for may not make it into future versions. That’s a big fail imho. ;)

All I want is to be able to install WordPress into a separate domain, but still access the site from the root domain. This is a fairly common setup that does not work in the current version of WP-Hive (0.5.2).

I can get it to work, but it requires manually modifying the code.

Given the reasons I listed above, it’s not worth the effort.

I’m going to back to the tried and trued VMB. ;)

If you don’t consider yourself technical I would definitely recommend WP-Hive. Within the past couple months the developer has _finally_ started development on a new version that should be released soon (tomorrow in fact). Some of the cons I listed will be fixed in the new version (e.g. support for sub-directories).

As for the lack of individual wp-config.php files with WP-Hive, that won’t affect anyone on the public-facing end. It is really more of a flexibility feature for the person maintaining the blogs. It gives them more options on how to organize the different blogs. Maybe you want each blog to be in its own database. Maybe you want some related blogs together in one but a separate database for the rest.

It doesn’t sound like you’d t care about that flexibility. So one database/login is probably fine for you.

It’s easy to get started with WP-Hive so I’d recommend you take it for a test drive and see if it fits your needs before considering VMB and some of the other options.

Hope this helps!

-Alex

It has been 7 or 8 months now, and I wonder if you are still happy with your switch to Hive?

I am trying to decide between VMB and Hive, and not being very technical, it is hard. I want to have over 50 blogs eventually, with several writers.

It seems for me the main difference is in what you said;

“Hive. .. does not allow a separate wp-config.php file for each blog. That means all blogs have to be installed to the same database with the same database login and no ability to easily customize the table prefix.”

Why does this matter? What could a blogger do or not do because of this difference?

Thanks, I appreciate your time.

It wouldn’t hurt to make that comment more prominent somewhere. Maybe in the readme or something. You have a ridiculous number of comments on the VMB post, so I’m sure lots of people will miss out on this tip.

And yes, build and expand on VMB. I’ll still be keeping an eye on its development. I have a special place in my heart for VMB since it was the first multi-blog solution that worked well for me. ;)

Keep it up!

I may just have to check out WP-hive for ideas. ;-)