BuddyPress.org

Just install buddypress with group forums and install bbpress seperate, with intergration offcourse.

There’s nothing wrong with that.

@Andy But from a usability point of view this is very confusing. Some activity streams do allow you to post into them and some don’t. One method of posting into a user activity stream is allowed (replies) but another (leaving a direct comment) isn’t. From a developer point of view this might feel logical due to the underlying structure, but from a user point of view it’s very confusing. A user is forced to jump through all sorts of hoops just to be able to interact with a friend.

I don’t think it would be confusing for the user at all to allow their friends to post into their activity stream. They are, after all, already able to do this by replying to an activity. Allowing users to directly post into their friends activity stream would merely add consistency to the user interaction. It’s precisely how Facebook works and they seem to get along just fine.

On the other hand, the fact that in order to see a comment on your own profile you have to browse to someone else’s profile does feel very confusing, because it all of a sudden injects twitter style functionality into a specific subset of the buddypress user interaction which otherwise is more consistent with how the majority of other social networking sites work.

You can certainly have a standalone install of bbPress along with BuddyPress and then integrate it with the site to give user table sharing and login sync.

But I would suggest to check how BuddyPress is going to handle this issue at a later date so that if you want to import it back to single system then you can because BuddyPress might support it then.

<?php if(!is_user_logged_in()){

nocache_headers();

header("HTTP/1.1 302 Moved Temporarily");

header('Location: ' . get_settings('siteurl') . '/wp-signup.php?redirect_to=' . urlencode($_SERVER['REQUEST_URI']));

header("Status: 302 Moved Temporarily");

exit();

} ?>

this quick hack (in the top of header.php) will only registered and logged in users can view. As for using it with version 1.2 default theme ~ I would suggest making a custom header for any of the buddypress elements you want to keep private and keep the rest public. At least until privacy functions are available as a plugin or in core.

wp2.9.2 here too. Very strange. I tried disabling all other plugins apart from buddypress and bp-lockdown, with the same result.

https://buddypress.org/forums/topic/security-all-site-data-visible-to-members-and-non-members-alike#post-39305

You keep bp-custom.php within your BuddyPress plugin directory? I have mine in the root of /wp-content/plugins/

This is a problem with regular WP, though. (WP 2.9.2 + BP 1.2.1)

On shifting my WP files from the parent directory (example.com) to a separate WP directory (example.com/wp/), Buddypress URLs contain a /wp/ in them, by default.

For instance, the admin profile url is example.com/wp/members/admin. Manually typing in example.com/members/admin will get you to the same page, without any errors, but all inks generated by BP contain /wp in them.

I actually found this quite difficult and still cannot convert a theme! Damn by technical capabilities.

I love these posts. So random. Build a child theme and change it to whatever your heart desires:

https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

I would say privacy is probably the most complex feature to implement – as far away from simple as you can get.

If you want to just close off your site to users who are not logged in, then there are plenty of plugins you can use. Or you can just use the following code in your plugins directory, smartypants:

<?php

/*

Plugin Name: BuddyPress Lockdown

Plugin URI: https://buddypress.org/

Description: Lock down your BuddyPress site if a user is not logged in.

Author: Andy Peatling

Version: 1.0

Author URI: https://buddypress.org/

Site Wide Only: true

*/



function bp_lockdown() {

global $bp;



if ( BP_REGISTER_SLUG != $bp->current_component && 'wp-login.php' != $bp->current_component && !is_user_logged_in() )

bp_core_redirect( site_url( 'wp-login.php' ) );

}

add_action( 'bp_init', 'bp_lockdown' );

?>

Update again: the full answer is now here – https://wordpress.org/extend/plugins/bp-template-pack/

You could always just use htpasswd to compel http authentication too. It’s a bit of a pain for users to have to log in to both the directory, and into buddypress, but it will give you the protection you need. Or you could just stick something into the theme to say that if the user isn’t logged in, they’re always redirected to the login / register page. I need something similar, so if I make any progress, I’ll post back here with it.

This sounds really intersting! I haven’t checked ur plugin yet, but i’ll definitely do so in the next few days.

I have one idea for a future version: A directory that shows the Items with most likes (6hours, Today, Week, Year)

I believe this would help people to filter through most important news on a crowded network.

Well, i get the same trouble and it looks like i get it after update to the last buddypress-version.

/register/ redirect to the homepage. I use wpmu – latest version. Anyone how knows a solution? Thanks for help! M

You could try the performance tips listed here:

https://codex.buddypress.org/getting-started/improving-performance/

Don’t know about image posting in activity stream but FYI you can use this for video https://wordpress.org/extend/plugins/oembed-for-buddypress/

With all due respect:

This would seem to me to not only be a critical aspect of any social network, but also a rather simple one to implement. Then again, I’m no coder.

Obviously this feature is coming, but it hasn’t happened yet.

For 1.2, Jeff Sayre is updating his privacy plugin http://jeffsayre.com/2009/12/05/buddypress-privacy-component-released/. That’s one solution on its way. Otherwise, you can implement a lot of “stop people seeing this” in child themes.

Is there any way to enable the activations mails in a Single WP like in MU?

It seems to me BuddyPress supports activation only in WordPress MU.

n i c e !!!

@Hempsworth: first of all, great job! The plugin is amazing! Thanks for sharing!

I have 1 feature request: I would like to be able to choose what activities the members are allowed to like. For example: they can only like forum posts and group creations.

Regarding limiting the likers to just friends, as long as you make it an option, I bet there’s a lot of people who might find that useful.

I definitely see 4 different usage scenarios for this:

1 – “open”: you can see the name of everyone who liked it;

2 – “mixed”: you can only see the names of your friends (” and x others” just like your example above);

3 – “closed”: you can only see numbers (total of people who like it)

4 – “private mode” (more a privacy setting than a real scenario): no one sees what you like except you.

Ricardo

@r-a-y Thanks for the clarification. Do you know why it was decided to implement it this way?

It feels very counter intuitive that you’re able to post replies into the user activity stream, but to post a direct message into the activity stream you have to use a completely different component (which is disabled by default) to have your message show up in the user activity stream in a roundabout way. And to add even more confusion, posting messages directly to the site wide activity stream conversely is possible without having to use any tricks.

I don’t mean to sound harsh, because I love buddypress and it’s an amazing piece of software, but it does feel like it’s a bit counter intuitive and inconsistent in this specific instance.