BuddyPress.org

BuddyPress member themes should be located under /wp-content/bp-themes/.

Please note, just recently this changed. Before, the BP member themes were installed under /wp-content/member-themes/.

Of course, it depends on which version of BP you’re running, but you should check to see if you have a /bp-themes/ or a /member-themes/ folder under /wp-content/. Then, make sure that you have an actual member-based theme installed in that folder.

You know the same thing is happening to me. I am trying to customize a theme. I know that the problem above has something to do with the problem I am having. What is happening is when an account is created you can log in, and see your blog. You can also get into the blog admin, but when you try to go to: My Account -> Profile — It says:

“You do not have any BuddyPress themes installed.

Please download the Default BuddyPress Theme and install it in /wp-content/bp-themes/”

In the BuddyPress settings the “Select theme to use for member pages:” is empty. I’ve been trying to figure out what is going on but I’m lost.

Now one thing I didn’t know if it was an issue or not was the path for the bp-themes folder is located in: /wp-content/mu-plugins/bp-themes/

The buddypress-member folder is in there. Could that be an issue? I personally did not install WP MU and Buddypress, so I wouldn’t know if it was some type of problem with installing everything.

If you are just using the default templates you will just be able to overwrite everything from RC-1 to RC-2 and then the same for 1.0 shortly after.

Using other themes from the default or your own theme will require some tweaking going from RC-1 upwards, but this is only because we are currently pre 1.0 and there are some last minute improvements.

Yea its pretty easier, as Paul said, just upload the files and replace them. Normally you can leave the templates alone.

However if your going from RC1 to SVN trunk then you need the new templates too. Its like this because this software is still in beta and things change for the better.

But normally with templates you just need to update the functions and header.php files (although don\’t rely on my advice)… just change them all and make sure any mods are made in custom.css and images are in a custom folder

But when v1 is ready you can update via the admin interface.

As Nicola said always make a backup first, i like to make a duplicate copy of my public_html / www folder.

wait for the rc2 release or if you can to the stable one,

or if you would like to try, back up your files and upgrade

Not really.

Pull a copy from the SVN – either the trunk, or a particular tag. Then to update in future, you can just use “svn update” basically.

Just ran a couple sites through the plugin move without any big problems. BP_PLUGIN_DIR and BP_PLUGIN_URL are nice additions.

The only thing I noticed is that the BP Core plugin needed to be activated first. I got some errors at first just clicking activate for the plugins from top to bottom.

Using the default BP Theme, latest WPMU 2.7 and BP Trunk … the FB Connect button is not showing when logged out as expected.

After activating the plugin and creating a fb application for my blog, I don’t see anywhere to enter the API Key or Application Secret. The only option in buddypress is to activate, am I missing something?

On the FB side, are there mandatory settings that need to be inputted other than Connect URL and Base Domain?

you have to put thoses lines in your wp-content/member-themes/buddypress-member/profile/profile.php to make it work like you want

you add this test :

<? global $bp;

if ( ‘is_friend’ == BP_Friends_Friendship::check_is_friend( $bp->loggedin_user->id, $bp->displayed_user->id ) ) {

?>

before thoses line

<?php if ( function_exists(‘bp_send_message_button’) ) : ?>

<?php bp_send_message_button() ?>

<?php endif; ?>

end then close the test

<? } ?>

Thanks for the clarification. I think there are two types of typical WP/WPMU/BuddyPress users: (1) like to run the latest bleeding edge on everything and (2) like to have a stable release that is easy to update.

Depending on the client and site, I fit into both categories.

And yes, “svn switch” is awesome — that’s how I update my normal WordPress.org installs every time a new release is ready (tagged). That workflow (svn switch with tagged releases) is a perfect setup for type 2 above since it’s mostly worry-free.

Again, from now on BuddyPress will ONLY work with WPMU 2.7.1+ so please use the 2.7 branch from the WordPress MU SVN repo. Link: https://trac.mu.wordpress.org/browser/branches/2.7

I’ve been using the 2.7 tagged release for MU, not the branch. Are you saying that going forward BuddyPress requires keeping our MU installs up to date with the 2.7 branch rather than using a tag (2.7.1 doesn’t have tag yet I noticed)?

Using the tagged releases is what I always recommend for normal WordPress installs since it’s usually a nice stable release with a clean cutoff at a version number, and doesn’t get committed to generally. But it looks like MU devs (Donncha) don’t tag as often as WordPress.org devs do, so maybe it’s a bad idea to rely on tags for MU.

I changed Wire to Wall, see my notes at https://buddypress.org/forums/topic.php?id=1877#post-9953.

Some useful ideas can be found here: https://buddypress.org/forums/topic.php?id=1651