No, not impossible. You’ll have to write your own plugins.
wpmu 2.8.2, bp 1.0.3, bbpress 1.0.2
I believe my integration is working as advertised but… when I delete a forum topic from a buddypress group it is removed from the group forum but not deleted from bbpress. Over time the bbpress forum will have a growing number of topics/posts that group admins think they have deleted (from buddypress) but actually live on in bbpress.
I’m not sure if tags within buddypress group forums are working. Tags can be added but I only find them available when directly accessing bbpress. While on the buddypress side, I’m not able to search groups for tags in the group forum.
Are these issues of a bad integration on my part or just limits of the current versions?
The Ajax redirect in this solution, with the register?s=1, had some annoying side effects that made it unusable. See the original thread for details.
Or did you fix that problem, sandeepdude? I’m a bit reluctant to try it again and find out that it’s the exact same code…
I’ll look for a solution in the next few days. Another way to show an Ajax message after redirect would probably be part of the solution.
This is awesome. I was just looking around the BuddyPress features and wondering why the heck there was no “group blog” feature. And then sure enough, somebody was already working on it. Thanks!!
Apparently a “full-featured privacy (authorization) component for BuddyPress” is in the works for a future release. I hope that includes an approval process, but member management in general seems to be very low on the priority list of the Buddypress developers and community. If you need it anytime soon, I’d look into developing your own plugins.
I’ve been testing GD Star Rating on WPMU and Buddypress and have noted a few bugs to Milan (the developer).
I’ve asked him to see if he can hijack the BP activity stream; so when a rating is made, instead of the default “User commented on the blog post Hello World”, it will change to something else like “User wrote a review for Hello World”… or something like that.
Since it’s one of the most complicated plugins to setup and understand, I’m not going to allow GD Star Rating site-wide so the issues that Kunal17 is having won’t be an issue for me.
Gpo1,
I am using GDStarRating on 1 of my blogs though not on buddypress homeblog. I want to use it with multiple blogs but several users are reporting errors on the authors homepage so I am waiting for a more stable version.
Anybody using this gdstarrating?
I’m starting a work at home community site. So far, it’s just the basic theme.
@gaganawhad, the “Skeleton component” is for BP plugins!
What you want is the BP Skeleton Member Theme, which can be found in:
/wp-content/plugins/buddypress/bp-themes/bpskeletonmember/
Move that folder to:
/wp-content/bp-themes/
Activate it in the WPMU admin area – “BuddyPress > General Settings” and you should be ready to start theming!
I’m with you carlmartin10. I’m running the latest WPMU and just updated svn for buddyPress and am still unable to get the avatars to upload or display. There’s a ton of results when you do a search on the problem, but pretty much all of them either tell you to update or set the permissions. If that doesn’t solve the problem, we’re pretty much left out in the cold!
Let me know if that works. It would go in wp-content/themes/bphome/css/site-wide.css
When I saw you all talking about using Javascript just to center a theme and give it a fixed width… I sensed someone somewhere along the line went down a rabbit hole 
LOL.
Thanks, that’s a better suggestion, not really much of a coder, just stumble across solutions..
If I find something that works I try and share that, but more often than not someone else has a much better idea, so not sure if its a help or hindrance……try to steer clear of javascript where possible though
Javascript?! Good lord. Just make a site-wide.css file with one line of code in it
body {width: 970px;}
Does that not work?
Have a look in your sitemeta table. There are some buddypress records you need to remove.
As there was no solution provided here and its been some time ago maybe this has been resolved, but its a problem that I encountered.
I haven’t fully tested this but after a hunt around I found a couple of techniquues.
Using javascript to refresh on resize between the <head> tags causes infinite loops in IE in some cases so that will not solve the problem.
I found out though that if you include position:relative in all of your main outer divs including body and body.directory in the IE fixes css files in the bphome and bpmember themes your problems should go away…
Let me know if this works for you….as I’ve only tested it locally and on IE7…
You have to edit it by hand. You can use the Firebug addon to Firefox to get help with which CSS-code to change.
As far as I know, you only need to do the editing in custom.css. It should override the original settings.
That might be the problem. You need to get WPMU working before worrying about BuddyPress.
Looking at the URL, it thinks you are trying to register a new hosted blog at “http://waapsols.com/”.
When you installed WPMU, in the installation screen it asks you for a server name to use. What did you enter? I am guessing you entered your server’s IP address?
If that’s the case, delete .htaccess and wp-config.php and drop the database, and try reinstalling, but enter “waapsols.com” during the installation.
The thing is: I only thought I had deactivated the bp-plugin completely (via backend).
I guess it was removed from the active_sitewide_plugins-field in the sitemeta-table in the database – but it was not removed from the wpmu_sitewide_plugins-field in the same table.
So the site still worked (no HTTP-500-error), and the umlaut-issue with the p2-theme remained.
When I then removed the bp-plugin-entry via phpmyadmin from both fields, the “main blog” didn’t appear anymore (error 500), but the two “sub blogs” I have still functioned. And the one sub blog with the P2-theme worked then without the umlaut-issue.
I hope this clears things up a bit.
So for me it is pretty clear that the bp-plugin somehow interferes with the P2-editor and causes the umlaut-issue.
I deactivated all plugins via phpmyadmin – in the sitemeta-table as well as in the options-table of the single blogs (there are 3 in my installation right now).
So the HTTP-500-Error disappeared. And all of a sudden the P2-theme worked properly as well.
This means: the regular deactivation via backend of the buddypress-plugin didn#t really work. The umlaut-issue with P2-theme seems related to buddypress.
HELP! Since I tried to reactivate the BP plugin I receive a HTTP 500 error when I try to reach the site… mpf!
I’ll check it. Thanks for the support!
You have said that the problem occurs on WPMU, and that it does not occur on regular WP. You have also said this problem is not caused by BuddyPress.
I haven’t got an install of regular WP to test this on, so I am going to assume it is either a WPMU issue *or* you are using an old version of the P2 theme.
