BuddyPress.org

Really looking forward to the new Achievements. I’m launching a new Buddypress site for an existing forum I run that is based around gaming, and they’ll love having achievements within the community too! (Especially the obsessive types that spend way too much time getting every single TF2 and L4D2 achievement on Steam…)

Ran into the same issue of 404 Not Found after activating BuddyPress on my WP installation on Ubuntu 9.10. Looks like the default Apache installation didn’t have mod_rewrite enabled.

To address this I did the following:

– sudo a3enmod rewrite

– sudo apache2ctl restart

– put .htaccess in my WordPress directory (/var/www) :

# BEGIN WordPress

<IfModule mod_rewrite.c>

RewriteEngine On

RewriteBase /

RewriteCond %{REQUEST_FILENAME} !-f

RewriteCond %{REQUEST_FILENAME} !-d

RewriteRule . /index.php [L]

</IfModule>

# END WordPress

– put the following in /etc/apache2/apache2.conf

DocumentRoot /var/www

<Directory />

Options FollowSymLinks

AllowOverride all

</Directory>

<Directory /var/www/>

Options Indexes FollowSymLinks MultiViews

AllowOverride FileInfo Options

Order allow,deny

allow from all

</Directory>

I haven’t tested to see if this is all needed or not, but that’s what my site has configured now and it appears to fix the issue.

I’m not aware of any precedent in plugins claiming to be BuddyPress compatible which aren’t

Mingle, a social networking WP plugin is one I’ve seen listed once a while in https://buddypress.org/extend/plugins/ when the plugin get’s updated. It doesn’t even claim to be BP compatible, it’s just tagged as buddypress.

Very promising plugin. A few issues I’ve found ….

The code to remove the “high-five” notification was commented out.

Gifts sent to my admin account don’t show under Gifts. This is happening for one of my users as well. Gifts sent to him or myself simply don’t show. It stills shows in the user activity stream who sent the gift however.

Follow-on question! On the BP install I’m currently working on, the following long list of plugins (all of which seem to be working flawlessly activated non-sitewide) do not even offer the option for Site-wide Activation.

Is there a reason (or reasons) for that? Is there any possible downside? Or are they fine the way they are?

BP Group Management, BuddyPress Album+, BuddyPress Forums Extras main plugin (but not sub-plugins), BuddyPress Like, BuddyPress Links, BuddyPress Profile Privacy, BuddyPress Rate Forum Posts, Custom Profile Filters for BuddyPress, Enhanced BuddyPress Widgets, External Group Blogs (written by Andy!), Invite Anyone, oEmbed for BuddyPress, Welcome Pack and WP-FB-AutoConnect.

I’ve just moved a localhost.localdomain install to a live server. It was easy as pie.

As I recall the steps: I moved the entire WPMU install to my live server, created an empty database. I exported my local database as SQL from PHPmyadmin, then opened up the export.sql file in Notepad++ and search-replaced all the URLs as necessary on the local file, then imported to the new, blank database.

I edited the wp-config file (and the bb-config as well) to update the db credentials and URLs, and almost everything just worked!

Once exception: I think I had to go into the Buddypress–>Forums setup and hit the button to setup the forums again for some reason, but after that, all was well.

The instructions here were helpful.

This would work moving between domains as well, of course.

Thanks for this clarification, guys. It was something I was wondering about too — the terminology had never been clear to me.

And I totally did not know this:

All BuddyPress plugins should be activated sitewide.

Just a quick note @MrMaz, everything seems to be working as expected on a live install (after the fix foxley recommended) so I think my earlier issues were a combination of having Friends functionality switched off and working on a localhost install (there have been some minor strange things I’ve found doing that).

Wait until BP 1.3 for official BP support for WP 3.0.

If you need this now, get WPMU and read the following codex article:

https://buddypress.org/forums/topic/install-bp-in-a-sub-blog

Gald It worked.

I see you have buddypress Installed on main site /center and enabled on the blogs using the config.

so, that’s why, It is showing the main site.

anyway, you can manage that using conditional like this

<?php

global $current_blog;

if($current_blog->blog_id != BP_ROOT_BLOG){

//remove action which was registerd by buddypress

remove_action( 'bp_adminbar_logo', 'bp_adminbar_logo' );



}



//add your own action here

add_action( 'bp_adminbar_logo', 'my_blog_logo' );



function my_blog_logo() {

echo '<a href="' . get_bloginfo('home') . '" id="admin-bar-logo">' . get_option('blogname') . '</a>';

}

?>

That should do it.

You will need to enable permalink.

Please login to wp-admin and go to settings->permalinks and change the permalink structure. As far as i see, it seems you are single Wp and your permalink is not enabled. For buddypress, It is required to be different than the default. Change it to anything other than the default and It will work.

hope, It helps.

All BuddyPress plugins should be activated sitewide. Since they depend on BuddyPress, they will only work with BuddyPress. This means they will only work on whichever blog BuddyPress is associated. So, although they are technically activated sitewide, they only work on the main blog–the blog that BuddyPress works on.

Now non-admin users can see Facestream admin options in console.

Yes, that is a problem with that plugin.

If you are truly using the default BuddyPress theme, and are logged out, then you should see a login box / create a new account area near the upper right-hand corner of the homepage.

Look at http://testbp.org/ for an example

This is a simple fix. Sometimes BuddyPress plugin developers do not set the proper plugin header tag to make their BP-specific plugins activated sitewide–which means that everyone with a blog has access to the plugin and not just the Site Admin.

So, go to the main files of each of the plugins in question and look for this in the header:

Site Wide Only: false

If you see that, then you make the following change:

Site Wide Only: true

Of course, if you do not even find that tag in the header section, then you add it.

BUT, before doing that, make sure you have deactivated the plugins in question. Once you’ve done that, make the change, save the file, reactivate, and it should now work sitewide only. This means that only the Site Admin will have access to the plugin settings and activation in the admin dashboard.

One final thing to do, since you’ve discovered this issue with these plugins, please help out the community by contacting each of the plugin developers and pointing them to this thread.

@MrMaz Great to hear 0.4 is just around the corner — I say wait until WP 3.0 is out for all around compatibility.

Feature Idea:

I really like the BP Group Blog plugin concept. I think Group Links would be awesome! This way each group can have one parent link category (or, optionally, be able to create additional subcategories for their group links as well). Of course, all Group Links would show up in the site’s activity stream and on the default Links Directory page.

What do you think?

Yellow notice at top in admin to “activate a BuddyPress compatible theme” remains present, even after child theme activation. Notice disappears when default BuddyPress theme is used.

@Ron R, @webfadds – Just add this to the style.css included in buddymatic, just below the other comments:

Tags: buddypress

Hi,

In the forums index how can i set up an excerpt for the group description in “<small> – <?php echo $listing->forum_desc; ?></small>”. Some of the users use huge descriptions and i do not believe such long texts are required for the forum index. Thanks. Also (and I’m sure I’ve seen this elsewhere but cant seem to find it now, how could I put the index above the latest posts. My coding knowledge is quite limited, to say the least…