BuddyPress.org

If you’re simply looking at sending a message, then you’re right! messages_new_message() is the way to go.

If you’re looking to modify this private message over time, you can’t do it via a function because such a function doesn’t exist; you’d have to modify the content via the DB. I’m probably just reading into your use-case a little too much!

@r-a-y, @Travel-Junkie I replaced Ray’s original code with Travel-Junkies as it was favoured by the majority. However I´m using a lot of pages and Travel-Junkies solution is only blocking the core Bp functions. In addition Ray’s post is no longer present. What do I need to add to block all of my pages for non registered users? where can I find Rays original code?

I thought that there was a solution on the Google Webmaster page: http://www.google.com/webmasters/ I think you can provide them the login and they’ll index it.

Just know that if you do that, then they’ll likely cache some of the “private” pages which makes it so they aren’t technically private since you could potentially find them in Google’s cache.

Exactly what I needed! Thanks!

Good News… I think I figured out the above, all though I still don’t know why I had to add it…

I added this:

if ( is_front_page () )
bp_core_redirect( ‘http://musicpln.org/pln-posts/landing/’ );

above

if ($bp&&($bp->current_component == BP_REGISTER_SLUG ))//buddypress
return;

and now it all works like a charm… I’m sure somebody can make this look cleaner that I did, but it is effectivley working now…

Ok, spending evern more time on this… I went back to the idea of using @r-a-y ‘s modified regestered-users-only-plugin… Now it is 95% the way I want except the homepage is not re-directing to the landing page… every other page does this…. probably has something to do with the home page being the activity stream??? I’m copying the key changes I have done to the plugin below:

// This is a base array of pages that will be EXCLUDED from being blocked

if ($bp&&($bp->current_component == BP_REGISTER_SLUG ))//buddypress
return;

if ( bp_is_register_page() || bp_is_activation_page() || is_feed() ||is_page(‘landing’) ) //buddypress)
return;

$this->exclusions = array(
‘wp-login.php’,
‘wp-signup.php’,
‘wp-register.php’,
‘wp-activate.php’,
‘wp-cron.php’, // Just incase
‘wp-trackback.php’,
‘wp-app.php’,
‘xmlrpc.php’,
);

// If the current script name is in the exclusion list, abort
if ( in_array( basename($_SERVER), apply_filters( ‘registered-users-only_exclusions’, $this->exclusions) ) ) return;

// Still here? Okay, then redirect to the login form
bp_core_redirect( ‘http://musicpln.org/pln-posts/landing/’ );

Hello BP gurus,
Just checking to see if any of you have any code examples for my privacy problem above… I would love to get this to work tomorrow before my launch… re: private community & redirect to different page for login (with login widget).

https://wordpress.org/extend/plugins/registered-users-only/

@r-a-y @Travel-Junkie

Ok, I’m still dorking around with this… the goal is to have my site a register only site. When people go to musicpln.org they will be redirected to the landing page (http://musicpln.org/landing1) which is a BP page with a login widget. I also would like the feeds to not be blocked.

This code goes in the function.php file:

function sh_walled_garden()
{
global $bp;

if( bp_is_register_page() || bp_is_activation_page() ||is_feed() || is_page(‘landing1’) )
// Where landing1 is the page slug of where I would like to redirect
return;

if( ! is_user_logged_in() )
bp_core_redirect( $bp->root_domain .’/’. BP_REGISTER_SLUG );
// my activity page is the “homepage” and I don’t want to show any BLOG(s)
}

add_action( ‘get_header’, ‘sh_walled_garden’ );

I would like this to redirect to the landing1 reference above (which includes the login widget) The url is http://musicpln.org/landing1

I saw that you put this code in a previous reply…

Where can I put this to make it redirect to the LoginPage above? How can I tie this altogether now?

@grosbouff There is the BP Followers Plugin by @apeatling for your reference

One difference between Friends and Followers is that Friends is in core while Followers feature needs the plugin to be activated.
https://wordpress.org/extend/plugins/buddypress-followers/
https://wordpress.org/extend/plugins/buddypress-private-messages-for-followers-only/

The other difference is Followers is ala Twitter following. The “follower” doesn’t need to be approved by the one he follows. While for “Friends” to connect completely friendship request must be approved by the other party.

when you checked the db – was the hide_sitewide set to 1 on those records?

looking in the BP core code for groups_edit_group_settings nothing updates hide_sitewide if changing the status level from private to public.

There are tons of different code edits in here. I am wondering which I should use for buddypress with multisite wordpress 3.0 and where to put it. I made my own bp-custom.php file, but it doesn’t seem to work. Is this file suppose to exist already? And if so it didn’t appear on my installation. :p At least not in the path wp-content/.

Thanks for your help.

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/

I have the same with 2.9.2/1.4.2.1. Is it fixed with new BP version ?

Anyone fixed this yet?

Ok, so I dug up a trac ticket on this and it’s be regulated to the PLUGIN category and not actionable -at least for a long time…
https://trac.buddypress.org/ticket/2244

Any MYSQL wizards out there willing to look into this plugin for BP?

This would be a highly desirable option from my stand point and I’m sure many others. The ability to auto-purge Private Messages and/or limit the amount would be great.