Skip to:

Why WordPress + BuddyPress is going to suck!

  • Shnooka30


    I spoke with a few bloggers and they are already talking about adding sub blogs and buddypress, which I think is great however. Most of these bloggers have no idea how to code or maintain a site and most never do daily backups.

    People were talking about BuddyPress taking over Facebook 2 years ago and I thinks it’s going to do the opposite. Social sites were great, but a lot folks are getting tired of them already and want to stick to just a few. Now everybody and there mother is going to have BuddyPress added to their blog and add yet another “You Must Register” on the site in order to leave a comment. Or “Create your own blog”

    Mu was great, because we were such a small community and most of us were knew a little about coding and css. Hell, just installing wpmu was a deterrent from the average Joe using MU and BuddyPress as it was a pain to set up.

    There are millions of blogs running WordPress and yet most blogs fail as people don’t have the time, content or understanding how to maintain a blog and now WordPress wants to give them a complex plug-in such as BuddyPress? Its going to suck to see millions of these sucky blogs adding BuddyPress over the next year or two. I’m also going to feel bad for the folks who set up there sub-blogs on a site that is run by someone who has no idea what there doing or stopped using the site or stopped paying for the hosting.

    I wish they would have just kept mu and wp separate.

    Anyways, just venting. Not sure if anyone feels the same way about 3.0 and the death of mu.

Viewing 8 replies - 1 through 8 (of 8 total)

  • r-a-y


    Well creating a network (basically MU) in WP 3.0 still requires that same deterrent-knowledge you speak of. Not everyone will be turning this on!
    However, bringing this functionality to the masses also sheds light to the project and more developers will be able to contribute to the codebase.

    I do agree with you about mass-communities! Not every community is going to be vibrant, but even those BP communities that have 10 active members is enough to warrant BP’s existence.

    You should also know that there are a ton of low-quality “sucky” blogs because of WordPress, so what’s the difference if there are “sucky” communities because of BP? ;)



    Hit it the nail on the head about deterrent-knowledge. I mean, I’m not the greatest coder out there… but at least I know a little CSS and how to read through forum posts before I post. Google is man’s best friend. :)

    I’m still not even sure how I did my first WPMU install. I think I must have tried 20 different combinations of factors before I got it running. Even then I didn’t have the presence of mind to write it down. :P

    Hopefully @r-a-y is right, that it’ll shed more light to developers.



    @r-a-y @paulhastings0

    I think it would have bean best to keep mu & wp separate and not merge the two. There is already a plug-in being developed that will allow sub-blogs the capability to add their own buddypress. So you would have a monster buddypresss site with multiple minor bp sites all on one domain.

    This is getting ridiculous.

    John James Jacoby


    Fact is that not every website needs to be a social network, same as not every site needs to be a blog network.

    BuddyPress, much like WordPress, shines when you don’t even know you’re using it, and it’s up to good themes to make that happen; something BuddyPress lacks when compared to WordPress.

    There are limitless setups that you could dream up with mutlisite WordPress and BuddyPress, but none of them matter if the theme can’t pull that functionality out to be front and center. Multiple blogs, sites, networks, domains, communities, groups, etc… I think it’s safest to mirror the development of your community similarly to how one prepares a server; react to the size and don’t over-prepare. If you have 10 users, you probably won’t need W3 Total Cache and a CDN. Once you have 10,000 active users, you may want to consider beefing things up. Same with BuddyPress; once you have a ton of users, turn on groups and forums, or add something new and exciting.

    Community features should match community size. If you turn on too many features with not enough users, your website looks like a ghost town, and no one will join. If you don’t have enough features, people will get bored and leave. BuddyPress does its best to let you find that balance pretty quickly, and helps you shape your online community how you see fit.

    It’s like SimCity, but without the natural disasters. :)



    If someone wants to make a monster buddypress install with small buddypress installs beneath it, let him.
    He’ll soon realise that it won’t work that way.

    Originality and feature rich buddypress installs will prevail. :)



    I couldn’t be more excited about the merge of mu into 3.0. Finally I can come out of the closet I’ve been hiding in for so long.

    On most forums, as soon as I mention that I run mu, I get the proverbial, ‘not supported’, argument, whether it’s a theme or plugin purchase, or even a simple question. I suppose in the long run I should be grateful for the treatment I received most places as it really has taught me to be more self-sufficient. I actually spend more time now learning how to code then all other activities combined. As frustrating as it’s been, I have to say it’s been more than worth it. It’s almost a joke going back a year or two and reading the questions I had on other forums. And to think.. at the time I was running hundreds of client websites. Little did I know just how little I actually knew. It’s also important to mention that the absolute best wp coders that I have met all either run mu, or are intimately familiar with it. Many of those people are here on this site. Their level of expertise is head and shoulders above the normal wp user.

    @johnjamesjacoby has it absolutely correct. The more time you spend on the theme of the site, and especially the back-end administration portion, the more the site really starts to shine. I’d say that I spend an equal part on modifying the looks and functionality of the backend as I do the theme. Basically every time one of my customers asks me how to do something that I believe they should be able to figure out on their own, I go back and try to find ways of making it more intuitive for them.

    Most of my clients don’t even know they are running wp/bp. They simply wanted internal group communication systems, and it just turns out that bp fits the bill almost perfectly. What better system could there be than a system where I can give a client who has multiple locations a series of sites all connected together, cohesive, and simple to use. Gone are the days of having to stitch together or bridge multiple systems. I’m so glad that I will never have to write or pay for another bridge script again, only to have one of the products die a slow death on the vine. I really believe wordpress and possibly buddypress are here for the long haul.

    It’s also important to mirror what JJJ said about site size vs. features. I have some very small client sites, where it would make no sense to turn on most features. Doing that would only confuse the users and make it look awfully lonely. Then again I have sites with thousands of users. Turning on most of the features for them would make perfect sense, as everyone finds their own little area of the site that they enjoy. Bp makes this very easy.

    @shnooka30 I’m actually one of those people who couldn’t be more excited about the plugins to give sub-blogs their own bp installs. To me, that is the biggest current downfall of bp, other than privacy and spam which are being addressed.

    The entire reason I went to wpmu in the first place was that it was horribly inefficient to run hundreds of separate installs. I spent way to much time having to update sites one at a time. Wpmu, literally saved me hundreds of hours a year in updating time alone. It’s only because of the plugin not being available yet that I don’t offer bp to many of my client sites. When the plugin is ready, then I hope to jump in with both feet. At least the wait has given me the time to get a real understanding of the bp code base before adding it to the mix.

    Bottom line is those who run undermanned or lousy setups of bp on shared hosting, which is the majority of users, will die off very quickly. Everyone else who does it right will appear so different in both appearance and service, that the public won’t even put the two together.

    Hmmm. I’ve seen other people waiting for the merge to use BuddyPress. Works fine on single WP already. Like JJJ said, it’s not for everyone.

    Neither is running a Network. :) It’s not obvious to enable for single WP users. They still need all the same knowledge they did before. The install process (to me anyway) actually now has *more* steps, since you have to install WP first, then enable the network.




    I spoke with a Developer here in Tampa that works for a newspaper and they have a semi-working version of it already. Apparently its a newspaper company that has news blog here in the US and South America and they want each news blog/location to have there own individual bp install on one network. The guy could have bean bs me, but it made sense. I also read you were talking to brajesh about trying to do the same a week or two ago, so it’s only a matter of time before it’s available to the wp users.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Why WordPress + BuddyPress is going to suck!’ is closed to new replies.
Skip to toolbar