Heres what I did:
(this is on a multisite – yes my host allows for e to execute php files and -press type programs, including wordpress and bbpress)
I deleted my old BPress for other issues that worked upon its deletion. I then searched and installed this version through the dashboard for network admin and then tried to network activate. the first tie I got that error, I then checked the permissions and tried an experiment by setting things from 750 – 777 for all files and directories (including sub directories) of my “upload to” folder. so this made all associated files with bp 777. I tried activating it again….same issue.
Thanks Boone Gorges!
A comment the line about enable multiblog and the wizard runs well. I really need the Multiblog feature in my website and I will uncomment the line after. I have problems to make BP-compatibility runs, but now they are solved.
This is a good idea for a feature enhancement. I encourage you to open a ticket, requesting that these slugs be customizable. http://trac.buddypress.org
@r-a-y What happens is what I described above. I NEVER activated BP Template Pack. It’s only installed for future use, that’s all.
Have you gone through the BuddyPress setup wizard? When you go to Dashboard > BuddyPress > Pages, is there a page associated with Members?
Very strange. Can you check your file permissions, to make sure that the web server can read the contents of bp-core?
Never had this before….
Fatal error: require() [function.require]: Failed opening required ‘/home/a5223693/public_html/wp-content/plugins/buddypress/bp-core/bp-core-wpabstraction.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/a5223693/public_html/wp-content/plugins/buddypress/bp-loader.php on line 68
Never seen this error before
@davidtcarson Sounds great! Will wait for the version in the repository then. I think your theme will become really popular since there’s a huge lack of good looking themes and since it’s a child theme to the original theme and thus easier to update. Thanks again for all your work and count on me to help spread the word!
is there a way to make bp redirect “subdomain.domain.com/wp-login.php?action=register” to buddypress register page?
this method of registering/login is bypassing my buddypress required profile fields and security.
i’m using WordPress 3.2.1 multisite activated and buddypress 1.5
i have been looking and searching for a LOONG time and i’n burnt…
could use some help please 
Is unhooking a difficult task?
@DJPaul did you know of a better way to do this? You had replied to me a while back on the blog post for beta 1 that it shouldn’t be too hard.
BuddyPress 1.5 – Beta 1
Hello,
I just noticed the link for http://buddypress.org/support/topics/mine/ gets a 404 page.
Users are the same even when you upgrade from 1.2.x to 1.5.
If you’re talking about an import users option for BuddyPress (not WordPress), that’s different. A plugin like that could be developed, but as far as I know, nothing freely exists at the moment. I could be wrong though.
Hello,
This really isn’t a BuddyPress thing.
Check out https://wordpress.org/extend/plugins/polldaddy/
Polldaddy is an Automattic ruckus http://polldaddy.com/

ok, saw a whole bunch of updates available so I switched to localhost for testing, everything went fubar, which is to be expected, still don’t know why certain CMS can’t evolve to keep themes separate from code, such as with MODx and other newer platforms, no big deal I have to rebuild the site and deploy it, easy, years of joomla and drupal make this second nature…unfortunately I can’t seem to use the import export features of my remote bp 1.2.10 install (current WP) to another bp 1.5 install. I was only able to import those who were registered as site administrators not subscribers.
The thing which upsets me greatly is that I had just developed a social site for a client not three weeks ago.
I have googled considerably, found some really funky workarounds and outdated plugins…but if buddypress releases such an important upgrade to earlier versions, wouldn’t the devs take into consideration that there are hundreds of sites already full of registered members which will have to be transferred? I must be missing something because surely that would be thought of…though I did see the possible features for the 1.6 roadmap…export import user data…does that mean I should wait for 1.6 before considering an upgrade?
and are there any fairly painless ways to import registered users into 1.5 without having to export tables, edit them and import? I thought about importing the mysql but doesn’t make sense since 1.5 seems to be a drastic change there are likely to be inconsistencies with older installs.
No, that is where i started.
I added:
define( ‘BP_DEFAULT_COMPONENT’, ‘sites’ );
to bp-custom and now it does.
so the page https://codex.buddypress.org/extending-buddypress/changing-internal-configuration-settings/ is incorrect.
I currently have:
define( ‘BP_MEMBERS_SLUG’, ‘clients’ );
define ( ‘BP_BLOGS_SLUG’, ‘sites’ );
define( ‘BP_DEFAULT_COMPONENT’, ‘sites’ );
//define ( ‘BP_IGNORE_DEPRECATED’, true );
//define ( ‘BP_ENABLE_MULTIBLOG’, true );
//define( ‘BP_DTHEME_DISABLE_CUSTOM_HEADER’, true );
define( ‘BP_SILENCE_THEME_NOTICE’, true );
//define( ‘BP_ENABLE_USERNAME_COMPATIBILITY_MODE’, true );
define ( ‘BP_DISABLE_ADMIN_BAR’, true );
in wp-config. all seem to work accept the default profile page.
ok, let’s give this code a shot. I just tried it on a local dev and it worked well.
Code:
function redirect_group_home() {
global $bp;
$path = clean_url( $_SERVER[‘REQUEST_URI’] );
$path = apply_filters( ‘bp_uri’, $path );
if (bp_is_group_home() && strpos( $path, $bp->bp_options_nav[‘groups’][‘home’][‘slug’] ) === false ) {
/*
echo "HERE WE GO…";
echo "<PRE>"; print_r($bp->groups->current_group); echo "</PRE>";
echo $bp->groups->current_group->status;
echo $bp->groups->current_group->is_user_member;
*/
if ($bp->groups->current_group->is_user_member || $bp->groups->current_group->status == ‘public’) {
//echo "<PRE>"; print_r($bp->bp_options_nav); echo "</pre>";
//exit();
if ($bp->bp_options_nav[‘groups’][‘announcements’][‘slug’]) {
bp_core_redirect( $path . $bp->bp_options_nav[‘groups’][‘announcements’][‘slug’] . ‘/’ );
} else {
bp_core_redirect( $path . $bp->bp_options_nav[‘groups’][‘forum’][‘slug’] . ‘/’ );
}
//bp_core_redirect( $path . ‘welcome/’ ); //quick hack for some other tab
}
}
}
function move_group_activity_tab() {
global $bp;
if ($bp->groups->current_group->is_user_member || $bp->groups->current_group->status == ‘public’) {
$bp->bp_options_nav[‘groups’][‘home’][‘position’] = ’98’;
$bp->bp_options_nav[‘groups’][‘admin’][‘position’] = ’99’;
$bp->bp_options_nav[‘groups’][‘home’][‘name’] = ‘Activity Log’;
}
}
add_action(‘wp’, ‘redirect_group_home’ );
add_action(‘bp_init’, ‘move_group_activity_tab’);
If that does not work for you can you kinda enable debug and comment out the /* and the //echo lines and see if you get anything different?
On a side note, I noticed you called them forums. Did you know that bbPress is now a plugin at https://wordpress.org/extend/plugins/bbpress/ if you don’t want all the BuddyPress features and just the forum itself? Just an FYI in case that serves ya better. Check out https://bbpress.org/blog/ for more as it’s new as of yesterday as an official release.
You need to create a WordPress network first before you can use BuddyPress’ blog tracking functionality.
Have you read this article?
https://codex.wordpress.org/Create_A_Network
BuddyPress 1.5 created pages for your directory pages.
In the WP dashboard, navigate to “Pages”, and try and find a page that says “Sites” or “Blogs” or whatever your blog directory is called. Rename the page slug to ‘sites’.
Then in your bp-custom.php file, use:
`define( “BP_BLOGS_SLUG”, “sites” );
define( “BP_DEFAULT_COMPONENT”, “sites” );`
After you’ve installed BuddyPress, what happens when you switch to the bp-default theme?
In the WP dashboard, navigate to “Appearance > Themes” after you have installed BuddyPress and select “BuddyPress Default 1.5”
Do not activate BP Template Pack yet. What happens?
Does BuddyPress function on the site?
You can throw in the following code in your /wp-content/plugins/bp-custom.php file:
`function my_group_avatar_default() {
global $bp;
// change ‘identicon’ to anything listed here:
// http://en.gravatar.com/site/implement/images/#default-image
$bp->grav_default->group = ‘identicon’;
}
add_action( ‘bp_init’, ‘my_group_avatar_default’ );`