Just a quick update. I’ve been waiting for BP v1.1 to come out so that I could tweak the Privacy Component code were needed. I plan on sending Andy my component next week. After the two of us have had some time to kick it around, I will release it for private alpha. That should be soon!
WordPress and therefore BuddyPress lack a lot of standard i18n features as core developers are mainly using English than other languages. They still haven’t figured out problems we have when we use our own languages within WordPress/BuddyPress.
Anyway, for the problem, there’s similar ticket on trac that names containing dots or dash don’t work on 1.1 environment. It may be related to this ticket.
In BuddyPress, all forums are still tied to groups, but now there is a group directory to assemble forums and topics in one central location.
I recommend reading https://codex.buddypress.org/developer-discussions/buddypress-forum/ if you haven’t already…
Peterkirn, did you choose a new installation or an existing one when you updated?
Here’s what’s happening, and how to fix it.
Since you picked new installation, your existing groups forums won’t work, because the forum_id’s they want to post to don’t exist in your new installation.
Basically, New installation = New database tables
If your old forums don’t have any important or relevent topics, or any at all, go back and forth between your “wp_bp_groups” table and your “wp_bp_groups_groupmeta” table, and remove the groupmeta entries with the group_id’s of your existing groups, that have any forum_id.
When you disable and enable the forums, it isn’t creating a new forum for them, it’s just turning off the ability. If you created a forum for an old group, and then create a new installation, the new database tables will be empty and your BuddyPress forums will look at those tables for data. If you use an existing installation, then BuddyPress will continue to use the old bbPress tables and allow an external bbPress installation to access them on its own, while letting the bbPress included with BuddyPress use it for its own purposes.
Now I feel bad that I ran out of time in late August / September and was unable to contribute to the test process, but that’s how it goes some of the time.
The reason I ultimately opted for a fresh install, even with existing groups, was that I discovered the option to *migrate* an existing install a) left bbpress as a separate install, which I didn’t want, and b) because we had opted to put bbpress’s tables in a database separate from the wordpress mu database.
So, the question is, how do we take these existing 25 groups and give them forums to connect to in the new bbpress-in-buddypress setup? 
copgarden: What were you upgrading from? How was your forum set up prior to the upgrade? I’m guessing there must be something different in your setup relative to mine.
Update – I have tried creating a NEW group and posting to that. That works fine. So I suspect that perhaps the issue is that the previous groups are trying to point to our old forums installation? I just need to figure out how to revert our existing 25 groups to whatever
In the database, how does BuddyPress 1.1 point groups at the appropriate forum in its new integrated bbPress install?
Actually, as I think about this, it makes sense that this didn’t work. Presumably, when you opt for a fresh install, it sets up bbPress inside buddypress but does not try to create any new forums. So how can I force those groups to create new forums, I wonder, if checking / unchecking doesn’t work?
On the same lines, for some reason – even though I opted to do a fresh install – the Forums link on the main homepage is still trying to point to our old forum install (that is, domain.com/forums).
http://noisepages.com
Great it works. Thanks for the help.
So how this forums different from groups?. To me it looks the same.
Did you create a group forum ?
To get a forum you must first create a group.
Did you activate “forums” in BP component config; ?
I really need bbattachments for my BP community, and I’ve already started work on porting it over to BuddyPress. There are a few hurdles to overcome, but I don’t think it will take too much longer. I’ll post more when I’ve got something for others to test.
Tore, you can feel free to send me that $100 anytime
If it’s a money issue how much do you need to make this a priority? I realize this may not be the appropriate place to bring up this topic so please contact me through my site if this is an option. It’s a needed plugin and if paying to help give the developer enough time to finish it is the key I am willing to look into that!
Elliott Design
Ok, I’ll write here a more precise description of what I did in case anyone has similar issues in the future.
There’s no restriction in registering email as an username in WPMU. The only place I’ve had trouble with the email address as the username is BuddyPress. However, there may be other places, since the @-character is tedious.
Anyway, since emails are unique in the installation, just like the usernames, they can be to uniquely identify the user logging in. The workaround the to problem is to use a separate username, and set the login procedure to use the email instead of username. Here’s a nice plugin for the task.
Of course this workaround creates a bunch of problems for me in the integration, since these usernames aren’t necessarily used elsewhere and use of the emails in this fashion is really a hack, but these issues may be easier solved in the authentication code, which is the most crucial component in the integration and where I want to concentrate all my custom settings. Or else I’ll have to figure out something else later.
I see….I am trying to get my head around the buddypress architecture now, and I guess I got confused from the readme in the skeleton package
It says
Copy /bp-example/ and bp-example.php into /wp-content/plugins/ and activate the plugin.
Thats why I tried to activate it.
Reading that, I figured it had functions “working” so you could see how some of the aspects of the plugin interact with the hooks/front end.
I basically assumed it was a barebones (working example) of several functionsk and calls…but now ooking at it…I assume the statement in the readme is a template to…basically saying “this is waht you put in your readme”?
Thanks for getting back to me
@ Mariusooms: Hahaha… I sent it as an email but perhaps he looked me up! 
I’m not sure if an open source movement wants to add money into the mix. But I’d pay $100 for a working version of bb-attachments for 1.1. And it would of course be released to the public after that (as long as the one doing it accepts it)
(if inapropriate or only good over at job board group, tell me)
Yes, I’d love to team up on this Boone Gorges. That’s the type of functionality I plan to add to the next versions.
Thanks for the input! I was confused when I posted the version information. I’m away from my main work computer right now so I can’t absolutely verify but I believe the version needs to be AT LEAST BuddyPress 1.1. The version of the plugin I posted does not work with 1.0.3.
I’ll update the plugin on Monday and confirm version information.
Were you able to resolve the problem?
I have a similar plugin that is fully WPMU and BuddyPress compatible:
SI CAPTCHA Anti-Spam
https://wordpress.org/extend/plugins/si-captcha-for-wordpress/
@alxjrvsgmailcom
This is about as detailed of a step-by-step set of instructions you will find. The rest is up to trial and error, and experience!
https://codex.buddypress.org/how-to-guides/upgrading-a-buddypress-1-0-theme-for-buddypress-1-1/
The group invite code in Welcome Pack 1.4 now just calls the BuddyPress functions. BP Bug?
Maybe if your avatar had a smiley friendly face like Jeff, he would have
Just kidding, it is a shame, since _ck_ has many plugins.
I suppose once a plugin has successfully been converted to buddypress by someone, we could track the changes necessary to make compatible bp-forum plugins? I have no idea how hard it would be to make them compatible…not looked at it myself.
I’ve talked to _ck_ and s/he was not interested in developing for Buddypress. 
Not even with payment for it.
Bad news.
