BuddyPress.org

I was able to disable this by changing the following lines of code in the bp-activity-classes.php file located in the buddypress > bp-activity folder:

starting at line 196 add WHERE component_name != ‘friends’ like so:

`if ( $limit && $page && $max )

$activities = $wpdb->get_results( $wpdb->prepare( “SELECT * FROM {$bp->activity->table_name_sitewide} WHERE component_name != ‘friends’ ORDER BY date_recorded DESC $pag_sql” ) );

else

$activities = $wpdb->get_results( $wpdb->prepare( “SELECT * FROM {$bp->activity->table_name_sitewide} WHERE component_name != ‘friends’ ORDER BY date_recorded DESC $pag_sql $max_sql” ) );

$total_activities = $wpdb->get_var( $wpdb->prepare( “SELECT count(id) FROM {$bp->activity->table_name_sitewide} WHERE component_name != ‘friends’ ORDER BY date_recorded DESC $max_sql” ) );`

hope this helps someone.

Read this again.

If you look at /bp-core/bp-core-adminbar.php, all the functions are defined.

eg. if you want to call the “My Account” menu, use bp_adminbar_account_menu()

—

For the register page, study how this page is built: wp-content/plugins/buddypress/bpthemes/bphome/register.php.

Regarding who is responsible for data, it seems there is a lot of misunderstanding about OpenID out there. I’m not the ultimate evangelist on all this, but 90% of these types of concerns have already been addressed by the real know-hows of distributed social networking.

OpenID does *not* mean everyone has access to everything. Rather, it just becomes a viable way to port information, when necessary or desired, more easily, as well as providing a way for an individual to be identified more easily at any given site — but, again, this doesn’t preclude telling every site everything. Trust is still a site by site variable.

Here’s a list of great reads (plus a web “TV” show!) for those interested in understanding what’s true and what isn’t:

http://factoryjoe.com/blog/page/12/ (old, but addresses some common concerns)

http://josephsmarr.com/2008/04/23/data-portability-privacy-and-the-emergence-of-the-social-web-web-20-expo/ (also old, but an original “diso” reference”)

http://www.sociallipstick.com/2009/03/a-proposal-for-a-conceptual-open-stack/ (social stack reworked)

http://factoryjoe.com/blog/2009/02/13/this-week-in-video-facebook-and-the-openid-design-workshop/ (a bunch of videos from the OpenID Summit)

http://thesocialweb.tv/ (periodic episodes updating the latest in diso)

The final thing I would add is, like it or not, distributed social networking (OpenID and the like) are _already_ here: Google, Facebook, Yahoo!, AOL, MySpace, and a host of other providers have already embraced OpenID, and the clock can’t be turned back. There are still a lot of variables to be worked out (such as “single sign out”!), but BuddyPress would do well to support it, if not because it is a highly useful technology, then at least to support the percentage of customers who are going to want (demand?) the technology.

Anyway, back to RPX and BuddyPress…

BP bar not working…!!!

This is what i did

I had a full integration – means i had copied all the keys from wp- config to bb-config accordingly.

I had done all other settings so that a discussion forum made in buddypress is shown in bbpress.

I uploaded the buddypress bar plugin to the my-plugin directory.

Added the code into bb-config

with the absolute path of FILE i.e include_once( ‘/public_html/wp-blog-header.php’ );

activated the plugin

nothing happened!!??

Did i miss any step??

At the moment the main reason is so you can follow your friends activity via the friend feed.

Privacy controls and more information about relationships between members are something that will come in future; the roadmap is worth a read to get the feel for these things.

Of course, things will get done in some order and in some time depending on what Andy Peatling (the only BuddyPress developer) decides to work on, unless someone contributes. A chap called jeffsayre is working on privacy features currently – hopefully that’ll work as well as he’s making it sound

What other 3rd-party plugins do you have installed and activated?

There is a growing list of plugins that interfere with the avatar uploading and/or cropping process within BP. See this thread: https://buddypress.org/forums/topic/faq-how-to-code-snippets-and-solutions#post-11864

Look in all “/wp-content/plugins/buddypress/” folders for files that end in “-templatetags.php”.

Looks like there is a codex page setup:

https://codex.buddypress.org/developer-discussions/buddypress-template-tags/

But nothing is in there. I’ll start filling that page in when I have some time on my hands!

Just added the first function, but there’s a ton more!

—

Jeff, question for you… say I wanted to add a sub-page in the codex to split up the many “-templatetags.php” files.

How would I do that?

https://codex.buddypress.org/developer-docs/custom-buddypress-loops/

Also, explore around the developer docs site.

Since this is an open source project, there is no one person responsible for documenting BuddyPress. Or put it another way, the community is responsible. It only gets done when someone takes the time and adds to the codex–but, the codex is growing each week. So, you can add to it as well!

I have just noticed another bug in regards to the date box.

It seems that BuddyPress will not grant any dates before December 14th 1901 (as of today – i am not aware of whether that date shifts as days pass).

Granted, not many people – if any – will be needing this date as long as it is used for birthdays. But there might be some other purposes where this is a real bugger.

Any fix on this (and the before mentioned)?

Because BuddyPress runs as a site-wide plugin, as it sits today you’re stuck with one site-wide member theme. This could be manually side-stepped pretty easily though, by creating a function in your functions.php file to hook into the function used to gather the active member theme, you could theoretically sneak your own directory path in there on a per theme basis.

Haven’t tried this idea myself, and it might not be that simple in reality.

Or.

COPY (not move) your bp theme into the normal themes folder. Now it’ll show up in the dropdown. Once there, select it, save, and voila.

Afterwards you can delete the copy.

(or you can do it with symlinks if you know how)

Well, yes, that’s the best way for the majority of BuddyPress users, I suspect.

However, you can work around by duplicating the BP Member Theme folder (/bptheme) into /wpcontent/themes. You don’t need to do anything else, but this should populate the list for you allowing you to save the member theme.

Or, if you know what you’re doing, apply the patch to fix this problem to your current release manually – https://trac.buddypress.org/changeset/1601/. If you do not understand PHP I would not recommend you do this, just in case you accidently introduce any errors.

I’m having the same problem.

I’ve got MU 2.8 and BP 1.0.2. I put the themes in the correct folder. I can activate the BP home theme inside the MU Admin, but when I go to choose a theme for BuddyPress, the only themes that show are activated WP themes.

I’ve deleted BP, dropped all bp tables from the database and reinstalled. Then deleted and reinstalled two additional times and tried basically everything suggested here to no avail.

It seems that the current “solution” is to wait for the BP 1.0.3 — is that the current suggestion?

He probably forgot to change the theme away from buddypress after deleting it. Leaving the tables does cause a problem, because then when you reinstall all the settings are still saved.

Report it in http://trac.buddypress.org if you haven’t already.

To clarify, this is something we’re going to be using for paying clients, not the public at large, so that should take some of the issues raised above out of the equation.

If anything, that alone would make me want to stay away from OpenID.

Don’t get me wrong, I think it’s great for newspaper sites etc where someone can log in to comment. But if I’m paying you money, I want YOU to be responsible for any data I send you, and only you.

Also, this is going to enable us to take away the 4 separate passwords / logins our paying customers need to use currently down to 2 for things like the forums, their website, billing, support, etc…. that is the main reason we’re implementing this…. otherwise we wouldn’t waste our time building something unless it was totally necessary….

Sensible and laudable. How come you can’t have one for all four and self-host it? (Honestly curious here!)

Also, if I’m logged into facebook on my computer, and close facebook

You tech genius wouldn’t do that, right?

I do this all the time. 99.99999% of the time, no one but me uses my computer. Once in a while, a guest comes over and looks something up, but it’s rare. But yeah, this is something most of us do. I never log out of sites when I’m using my computer, logged in as my user name.

Thank you DJ Paul for your reply, I didn’t open an other thread because the discussion was the same.

Ok waiting for 1.0.3