BuddyPress.org

https://wordpress.org/extend/plugins/bp-profile-widget-for-blogs/

@Modemlooper – it’s already being rewritten in a way in versions BP1.2.4/BP1.3-bleeding … started between BP trunk-r2990 to trunk-r3000. Pleasant surprise.

Actually, this site is a good example of what I’m looking for. Some of the plugin groups have forums and some do not.

Here’s a plugin without a forum: https://buddypress.org/community/groups/wibstats-statistics-for-wordpress-mu/

How would I disable forums for certain groups on a normal BP site? Basically I want forums for groups to be disabled by default, but then to be able to activate forums for groups on a case-by-case basis.

There are no alternatives to Group Docs plugin at this time that I know of. How about contacting plugin author to see how you can resolve problem you have with the plugin. As he said “Reporting bugs is the only way for them to be fixed.” https://wordpress.org/extend/plugins/buddypress-group-documents/

I had a new fresh install of WordPress 2.9.2 and Buddypress Version 1.2.3 all working together fine, then I added a plugin, WP Featured Content Slider Version 1.0 and thats when I had an issue with cropping members avatars and group avatars.

The image would upload but the cropping window wouldn’t appear, just two copies of the image one the upload size and one a cropped size would show.

After deactivating the new plugin, the cropping function worked normally again.

It’s because you’re installing on http://localhost/ — that won’t work (it might be fixed in WordPress 3.0, not sure), it needs to resemble a full domain name i.e. something.com. I have an alias setup in my /etc/hosts file (if you’re on Windows, Google for the location of this file. I think it’s in /system32/) for “example.com”.

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.

+1 for using wp 3.0 fully.

Am interested in this as well.. Will content types be integrated into BP?

So, groups can have instances of able to post text, photos, videos, polls and such…

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.

Everythings possible as long as you can code it (or when your wallet is big enough).

This might help you out a bit, but to get all your specific functions, you’ll have to do some coding.
https://wordpress.org/extend/plugins/new-user-approve/

@shnooka30
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.

Well, I’ve been frustrated by this now for weeks and no-one seems to want to try and help. Let me describe two scenarios that demonstrate the two problems above in the hope that someone will try to solve them:

1. I have just installed a completely fresh WP 2.92 and BP default 1.2.3 on my local server (localhost). I followed TO THE LETTER the instructions given on https://codex.buddypress.org/getting-started/setting-up-a-new-installation/. Permalink is set to the first non-default option. The install went well and the site looks good. However, Clicking on the menu items Members, Groups, Forms, Activites etc gives:

HTTP/404
The requested URL alias for /members/ is not defined.

Question: What do I do to get the pages display properly?

2. I Have a live site waterwaywatch.org which fares somewhat better. I can get as far as Member and Group pages but if I try to click on a member to display their profile, the site re-directs to About.

Please, please, there must be someone out there who can help me on what both seems to be fundamental path issues. In both cases .htaccess contains:

# BEGIN WordPress

RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]

# END WordPress

Thanks in advance

Will

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.

I’m not sure what this has to do with BuddyPress, but there’s probably no need to cross post this.

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.

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