Trent,
I just want to say thanks, this solved all my issues, and it is working beautifully now. You rock!
You are running on windows right? Just a guess. Before installing bp you need to get mu running properly. It’s a pain on windows. What package are you using? WAMP?
To get your subdomains to work you have to edit the ‘hosts’ file in windows for *each* blog you want to have running on your windows box. The hosts file is in:
Windows 95/98/Me c:windowshosts
Windows NT/2000/XP Pro c:winntsystem32driversetchosts
Windows XP and Vista c:windowssystem32driversetchosts
Once you find it you have to create a line for each blog so:
127.0.0.1 ourcommoninterest.dev
127.0.0.1 adminstoy.ourcommoninterest.dev
That’s a sample from my laptop which I use to play with new things in mu, buddypress and bbpress. This is only the beginning of your problems on windows. I know I went thru *all* of them.
However, for now, you should replace the domain name with your chosen domain name. Replace the subdomain name with any blog subdomain name you’ve chosen. ‘trial’ in your case.
Try reading up on what it takes to install mu. Then what it takes to install mu on windows. Google finds lots of things related to mu. Here’s a start:
https://mu.wordpress.org/forums/topic.php?id=4624
You also need to follow the directions in the mu readme.txt file as it relates to apache.
Burt, I got the alphabet letters to be blue instead of orange. Thank you.
Sorry I couldn’t figure out the freenode thing. I got a client and connected but was denied. I guess I don’t have a user account? Well, anyway, I’m happy with the forums. I’ll try to wait longer before I post, so you have more time to answer.
Thanks again for the help.
Also, in the interim you could use the forum RSS feeds for notification.
This function isn’t in BuddyPress yet as far as I know but it should be a pretty easy addition. I’d create a ticket on the Trac (trac.buddypress.org) marking this as an enhancement.
@gogoplata wonderful! Glad to hear a forums success story once in awhile.
The hosts file can be edited through Plesk. You must be logged in as root then go to Virtuozzo->File Manager then navigate to /etc/hosts and you can edit it from there. That’s how I did it and can confirm it works, but make sure your changes stick. I modified it once and the server changed it slightly after saving which still prevented the forums from working but I re-edited as outlined above and it fixed my forum issues. Thanks!
dont confuse forums..
here we’re according for invitation module..
and if someone is interested to hire me, i will develope this plugin
ps: now i will watch for that, thanks 
Thank you Trent! I’ve been working on getting the forums working since they were first released and have FINALLY got them working thanks to your post and this thread. Looking back I think I had two problems:
1. I had been installing the plugin in bb-plugins, not my-plugins. I had seen my-plugins mentioned a few places but thought maybe it was replaced by bb-plugins in 1.0 and never really looked into it. I still installed and activated the plugin successfully through bb-plugins so I’m not sure if this was or wasn’t the problem but in any case thanks for pointing this out.
2. I previously modified the etc/hosts file mentioned in the other thread but it must not have saved correctly on the first try. I re-edited it to what burtadsit recommended and now we’re working.
Anyways, thanks again!
sorry to jump in..maybe most of us are interested in media plugin for user profiles! if you adapt (all in one) plugin for user profiles.take a look at forum on media. we could hire you..
Well, you can look at this post for a quick hack to only allow members to see anything on member profiles, groups, etc. That post has a hack that applies to the /wp-content/member-themes/buddypress-member/ theme. The buddypress-home theme in /wp-content/themes/buddypress-home/ doesn’t get the hack
You could apply it to buddypress-home theme in certain places if you don’t even want them to be able to search the blogs, groups, members, etc. but that would be a little harder to follow.
Then, on private blogs, I just use more privacy options so that private and no search engine blogs don’t show in any listings around the site. You can hack the code to actually list them in buddypress if you want, but default pattern is to not show them.
So basically, I would set the privacy for all blogs you don’t want showing and leave the main blog open. It is done with that plugin on a blog by blog basis.
Once Andy puts more of this into the core, it will be much easier, but for now we have to “hack” around a bit
Trent
That’s really helpful, Trent. I ran into that bug (your #7) many times and think that is what caused most of my trouble getting the group forums to work.
You might get a little more mileage for this one if you post over in the bbPress forums at https://bbpress.org/forums/ with more eyes for errors 
burtadsit,
I’m running on a shared host and I can report the same issue. Seems like the actual BuddyPress forums on the testbp.org site are appending a unique forum id, which is not happening for me, most probably because forum posts aren’t posting. A vicious cycle
Are you running on a shared host or a dv?
Check these topics. Not for a solution, but to know that a lot of others are having the same problem and trying to find a solution:
Group forums working yet not working
Group Forums will never work on some hosting providers
I’m getting the same error too.
i think that you’ve to ask in wordpress-mu forum, not here..
I got the same problem here. I am trying to find a solution.
Ya, my prob wasn’t media temple. It was me. I didn’t realize that /etc/hosts was consulted first when looking up an ip address. Thought it all went thru a name server. So it was finding a generic 127.0.0.1 address for my domain. First, and using it of course. Just stupidity on my part.
Just chiming in to say that so far I haven’t experienced any issues with mediatemples shared hosting. xmlrpc is working swell too with the iphone app.
I think he’s talking about *how* domain names get resolved on a shared hosting provider. I ran into problems with domain resolution on my DV. In my case it was just a matter of changing the /etc/hosts file. Since I don’t know what I’m doing in root, it took days to figure out what I needed to change to get xmlrpc working.
I think he’s saying that domain resolution on a shared host can be difficult to control by the user. Me or you as the user on a shared host. Simply because I have a domain hooked up to an ip address doesn’t mean that I have control over *how* that ip address is determined.
1. Lookup ip here in the internal net of the shared provider
2. Lookup ip there in the provider’s name servers
(Return the first ip that I find above)
I think what he’s saying is that the above process will not return the correct ip for the low level stuff that is happening in xmlrpc.
I’m just kinda hazy at the moment as to why the internal ip address is not valid for xmlrpc.
I don’t get it. What’s the problem? The forum stuff is still using the full domain name, so any POSTs and such will still go to the right domain, regardless of whether the IP is 192.168.0.1, 127.0.0.1 or 69.93.219.170. I’ve got the forums working on my server just fine, and it doesn’t resolve the internal requests any different than external.
Bonjour à tous, la traduction française est bientôt mise à jour pour le nouveau fichier .po disponible dans le dernier trunk en date.
Mise à disposition prévue: vendredi 19 décembre, dans la mesure où le fichier aura été testé avant. Simple question de disponibilité personnelle. Merci pour votre patience.
@bebopcool,@mandriam: j’utilise pour l’instant WMPU 2.6.5, ce qui n’a aucune incidence sur la traduction française de BuddyPress. Par principe je préfère tester sur l’avant dernière version d’un logiciel(généralement plus stable), quand la nouvelle version vient juste de sortir. La 2.7 pose en effet quelques petits soucis, si j’en crois les premiers à l’avoir testée ( https://mu.wordpress.org/forums/topic.php?id=10163&page=2 ).
J’attendrai pour ma part la 2.7.1
