BuddyPress.org

Have you *got* a http://domain.com/wp-content/plugins/buddypress/bp-forums/bbpress/ folder?

Can you upload a screenshot and a ticket to https://trac.buddypress.org/? I don’t run a Windows PC so I can’t use IE.

There was a bug with WPMU reporting this message, but it still activated the plugin correctly.

If that’s not the case for you, we need more information: https://buddypress.org/forums/topic/when-asking-for-support

Without seeing your error logs, it is impossible to help.

Be sure you are following these upgrade instructions *exactly*.

I downgraded back to 1.01 – and it’s running again. I REALLY need the functionality of 1.1 – any idea why this is happening or if this is a glitch with buddypress that might be fixed soon??

-Don

http://donelliott.us

I did the automatic upgrade from 1.03 and now my client’s site won’t load anything…just a white screen… http://oppositesdo.com/

What is going on? I can’t figure it out….

…and it rocks! Thank you!

I received that error when upgrading due a plugin conflict, however, even though I received the error, it still activated BP under the new version.

So – in 1.1 BuddyPress does not query the database to fetch avatars, it expects them to be in specific folders and with specific names.

Likely what it happening is the permissions on the folders denied BuddyPress the access it needed to move avatars around and into the format/location needed for 1.1. Most of the problems will be related to group avatars mixing up with user avatars, as they were in the same folder for 1.0.

The quickest option is to remove the /wp-content/blogs.dir/1/files/avatars/ directory and let BuddyPress rebuild your avatars as people upload again. Anyone who has a Gravatar will revert back to that image, so not all will be lost.

Other than that, you can use this code below to place group avatars in the correct place, so they don’t conflict with user avatars (this normally runs on upgrade). Make sure the permissions on the avatar folder allow for BuddyPress to move files around.

function move_group_avatars() {

/* On upgrade, handle moving of old group avatars */

$groups = groups_get_all();



foreach ( $groups as $group ) {

/* Don't fetch and move gravs, default images or empties */

if ( empty($group->avatar_thumb) || strpos( $group->avatar_thumb, 'gravatar.com' ) || strpos( $group->avatar_thumb, 'identicon' ) || strpos( $group->avatar_thumb, 'none-thumbnail' ) )

continue;



$start = strpos( $group->avatar_thumb, 'blogs.dir' );



if ( false !== $start ) {

$avatar_thumb = WP_CONTENT_DIR . '/' . substr( $group->avatar_thumb, $start, strlen( $group->avatar_thumb ) );

$avatar_full = WP_CONTENT_DIR . '/' . substr( $group->avatar_full, $start, strlen( $group->avatar_full ) );



if ( !file_exists( $avatar_thumb ) || !file_exists( $avatar_full ) )

continue;



$upload_dir = groups_avatar_upload_dir( $group->id );



copy( $avatar_thumb, $upload_dir['path'] . '/' . basename($avatar_thumb) );

copy( $avatar_full, $upload_dir['path'] . '/' . basename($avatar_full) );



unlink( $avatar_thumb );

unlink( $avatar_full );

}

}

}

add_action( 'plugins_loaded', 'move_group_avatars' );

Put that somewhere so it can run, maybe temporarily paste it at the top of bp-core.php, then remove it when you are done.

I think the comparison, in that case, would be wordpress vs. drupal, and then drupal social vs. buddypress…

I could be wrong, but this is technically your second major plugin.

Any tips on getting bp-events 1.1 working with BuddyPress 1.1? Or is it simply not finished?

I installed it fine but it’s somewhat broken. For instance, nothing shows up on the event detail pages. The content area is just blank. Anyway, if it’s still in development… that’s fine. I’m just trying to figure out the status… is it’s just not done or it I didn’t install it properly.

@philbow

I totally agree, this feature should be made more visible and being availabe at nearly all pages….

First, great job to everyone involved! I do have a question/observation.

Playing around with the testbp site, I notice that the status form is not visable. You need to click the current status to create a new “status post”. I’m wondering why it’s not always shown, like on all the other sites that use this feature?

I love this feature, but fear it won’t get used because users won’t realize that it is there (or how to get to it).

Not in the RC, use the final.

I just downloaded and upgraded to 1.1RC, yet I still don’t see some of the functions, specifically “bp_is_profile_component”

@bobblegom I am BP all the way but shouldn’t you compare Google Trends on “drupal” vs “buddypress” not “drupal social” ?

@candydate I just see the release of 2.7, 2.8 all the way to 2.8.4, all of @donncha’s hard work and the aforementioned community buzz and conclude that the wp community is not moving slowly.

I run a BP community of USMA alumni and not only is it stable but they generally love it. I am more of a hack than true coder and I have had no issues. It is def a serious professional grade tool. The ease of customization alone (I have many friends who run Drupal sites and it’s always fun to hear them defend the arcane way Drupal does things.

WP and BP have a lot of growth ahead and they are by no means perfect but the openness and willingness to change and grow is evident (just see any IRC chat with all the developers)

Happy to answer more specific questions on resource requirements and what you were not able to learn from your dummy site.

Here’s Andy’s announcement post about the just-released BuddyPress version 1.1. I think it speaks volumes about the current state and future health of the WPMU + BP community.

There is some hate in that linky, wow!

Which BP version are you using?

This is fixed in BuddyPress1.1.

I’m closing this topic since there is another one announcing the official release. Please route your responses here going forward.

If you are using 1.1rc or 1.1 trunk, then that should happen automatically for you once you turn on and configure the group forums.

If not, and if you’re using an unmodified version of BuddyPress 1.0, upgrading to 1.1 would be the easiest way.