The skeleton component does works if you activate it, it does provide some basic functionality as an example.
The error you are getting sounds like the plugin is being activated twice. Delete the plugin and reload the plugin admin page. This should make sure it is completely deactivated.
Re-upload the plugin – make sure bp-example.php is in the plugin folder root, along with the /bp-example/ folder. Try re-activating.
Private and hidden forum posts do not show up in the forums directory regardless of your logged in state. This will probably change in the future but there was not enough time for 1.1.
There is a bug that will not allow you to post on private and hidden group forums in 1.1, this is fixed in trunk and will be in 1.1.1 which will be out soon.
Super cache is not a good solution for BuddyPress since the pages are updating all the time and the cache becomes poisoned too quickly. Object cache is a much better approach.
It is not defective. Many people have set it up with no problems, you need to provide more details on your WPMU version and setup, as well as your server setup. Without this you are just shouting and no one can help you.
If you have deleted /wp-content/bp-themes and have activated bp-default in “Appearance > Themes” then this should not happen. If it does then there is a bug.
If you moved the installation this is going to cause problems, you will need to change a number of things in the database. This is no doubt the cause of your issues.
Jugoretz: I would definitely play more on a development server, get things up to speed then push it on the live site. If you’ve made a lot of modifications and customizations then with this version you will unfortunately have a more difficult upgrade path.
The way things work in 1.1 are much more solid moving forward, but they may cause some people who are heavily invested in 1.0 a bit more work.
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;
The first is correct, once you activate the bp-default theme you will no longer see this warning message, it is simply for backwards compatibility. Make sure you do not have a /wp-content/bp-themes/ directory.
