If you build themes, upload them to the WordPress theme directory and tag them “buddypress”. They will show up on this site once approved.
BuddyPress does run on WordPress MU, you know 
It’s the main blog.
I thought we would use..buddypress.org and wordpress for theme hostings
I’m sure that within the next few years there will be a ton of BuddyPress themes out there. It’s just too new right now. 1.1 just came out last week. But it’ll happen. Just look at the millions of WordPress themes out there. And all those theme developers can “hit the ground running” with BuddyPress. Especially with 1.1… which is much simpler to theme than 1.0. Doing a BuddyPress theme is basically the same as doing a WordPress theme… just with more templates (Profile, Directories, Site Activity, etc.).
Also, it’s only natural that the first few themes available will be pretty simple re-workings of the default. Again… I think it’s just a matter of time before we start seeing really different high quality themes… like with WordPress. Elgg on the other hand will probably never had any good themes because it’s next to impossible to theme. Every Elgg theme I’ve ever seen is just a simple (ugly) re-work of the ugly default. That won’t be the case with BuddyPress.
There is only one official site for BuddyPress discussion and that is this site.
bp-dev.org is a private site run by one of our moderators–Nicola Greco. He started it after he personally created several, early plugins for BuddyPress. I believe it served as an early plugin repository before BuddyPress plugins were hosted on WordPress.org.
There are already good themes for buddypress. I guess you haven’t searched enough. Core teams should focus on development, not themes. Since 1.1 theme design got much easier than before, so any wordpress theme designers can design.
Ha 
BTW… 2 seconds of searching on Google and I found a plugin to allow users to use their email address to login. I’m going to be plugging that in for sure. One less thing for users to have to remember and bug me about.
https://wordpress.org/extend/plugins/wp-email-login/
I find it all somewhat confusing as well… First Name, Last Name, Nice Name, Username, Email… too many options. I think it’s much better from a usability point of view to sign in using your email address… because users don’t remember usernames. But that has nothing to do with BuddyPress. The way login works is a WordPress thing I presume.
Dashboard is part of WordPress. Ask on their forums.
We have the same problem. I think, it’s a problems with the nice-names in the profil of WordPress MU. If the username (for example:timschmi) and the nice-name are the same, there is no problem. If the nice-name is different (for example:timschmidt) buddypress will link to timschmidt and not to timschmi. You can see it if you roll over the links.
Exactly Andy. That’s my issue. Hacking the parent function.php file is easy. But I don’t want to do that. So I created a function.php file in my child theme but the unregister_sidebar() function doesn’t seem to work 
I suspect this is a WPMU thing… not a BuddyPress thing. Here is the code I added to function.php in my child theme. Should work. Doesn’t. I’m at bit of a loss. I tried adding different priority levels to add_action() and they had no effect.
<?php
function remove_sidebar() {
unregister_sidebar('third-section');
}
add_action( 'admin_init', 'remove_sidebar');
?>
p.s. https://codex.wordpress.org/Function_Reference/unregister_sidebar
Hey Guys, I still can’t get this to work? I am on bp ver 1.1
Maybe things got changed in the update that would effect the way this works? I really need to have custom pages for this to work for my site. Again, to recap, here is what I have done:
put the below code into : (wordpress mu and buddy press are installed into subfolder)
mysite/subfolder/wp-content/themes/bp-sn-parent/functions.php and created a page in the same directory called dashboard.php
CODE:
// creates custom page
define('BP_DASHBOARD_SLUG', 'dashboard');
function bp_show_dashboard_page() {
global $bp, $current_blog;
if ( $bp->current_component == BP_DASHBOARD_SLUG && $bp->current_action == '' ){
// The first variable here must match the name of your template file below
bp_core_load_template( 'dashboard', true );
} }
add_action( 'wp', 'bp_show_dashboard_page', 2 );
//
end custom page
URGENT: Need to figure this out!!!!
As much as I can tell, being one of those English-speaking imperialists to which you refer, WordPress has a good range of i18n stuff if developers use the right functions. If you think WordPress and BuddyPress seriously lack in these areas, then please by all means start a specific discussion thread on each product’s forums or file trac tickets/bug reports/patches.
Back on topic, I think socialpreneur’s on the money with this.
I am going to try a fresh install
of wordpress mu , the buddypress
starting over fresh
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.
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?
I’m my case… I’ve simply decided in home.php to wrap the “first-section” widgets with logic that will show that widget section only to logged in users… otherwise it is replaced with a positioning statement + calls to action (i.e. Join! Donate! Learn!) and a wordpress loop. Pretty simple stuff:
<?php if (!is_user_logged_in()) { ?>
[static content & wordpress loop for the public]
<?php } else { ?>
<?php if(!function_exists('dynamic_sidebar')||!dynamic_sidebar('first-section'))
>
[widgets for members only (i.e. site activity) ]
<?php endif; } ?>
Looks great, when will it be released for further testing?
When checking a classified detail, I getthe following error:
Warning: Division by zero in /home/benoitgr/public_html/dev/wordpress-mu/wp-content/plugins/bp-classifieds/bp-classifieds-templatetags.php on line 191
Cheers
The plugin is proof of concept code, you need to decide under what circumstances you want to allow group creation. At the moment, as you say, everyone is restricted… perhaps you want to base it on user capabilities? Have a look at the WordPress function current_user_can (support forum tag) and use this in rgc_validate_group_creation something like this (untested):
// Stop the creation of a group unless the current user can manage options
function rgc_validate_creation( $allowed, $group_details ) {
// User is OK to continue if they can manage options
if ( current_user_can( 'manage_options' ) )
return true;
// Otherwise they can't
bp_core_add_message( 'Sorry, you are not allowed to create groups.', 'error' );
return false;
}
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/
The is a filter that needs to be added to wpmu to resolve this issue. There is already a ticket that discusses this:
https://trac.buddypress.org/ticket/1103
That buddypress ticket includes a link to this ticket in for wpmu:
https://trac.mu.wordpress.org/ticket/1120
I’ve just faced this same question in this thread: https://buddypress.org/forums/topic/buddypress-says-themes-are-missing-but-they-arent
The answer seems to be yes, but it feels like quite a convoluted process. I understand the ethos from a design standpoint as to why they want a Buddypress theme used as the primary theme on ones WordPress site, but I really feel that this is an inflexible approach for those who have well-established WordPress sites already active.
If you use this on Buddypress be sure to update to the latest version of SI CAPTCHA Anti-Spam
https://wordpress.org/extend/plugins/si-captcha-for-wordpress/
== Changelog ==
= 2.0.4 =
– (03 Oct 2009) – Fixed session error on the members and groups pages on Buddypress versions.
