BuddyPress.org

I cannot get the PM system to work at all either.
I have tried rwo fresh installs of WP 3.0; installed the BP 1.2.5.2 plugin; used the default BP theme; changed the permalink setting to something other than default.

I can fill in the form to send a PM but nothing gets sent; nothing gets received; there are no messages in the database tables.
Other functions like Friends and Groups seem to work but I need PM.

I don’t get any error messages on screen and there are no error messages in my server’s log files.

There must be something missing in the set up instructions if a clean install doesn’t work. I’m not the only one.

Well it doesn’t appear that easy to reproduce as I’ve just tried on my production server test site running WP 3.0 and BP 1.2.5. Created a new group, set it as hidden, Added an update, and a forum thread and there is no sign of the two pieces of data in the activity stream.

This is why detail is vital, this is a serious issue if true and as I’ve said one that I first discovered and reported in the Trac a while ago, a solution was tested and as far as I was aware eventually committed to a version release, if not this has to be looked at again.

When you see these pieces of data are you logged in as a member who is a friend of someone who belongs to a hidden group as this was the issue originally.

How are non members of hidden or private groups seeing this, how is it “getting outside” Steps to reproduce this would be helpful as this is an issue I raised a ticket on quite a while back but it may not be exactly the same issue.

@sadr
https://wordpress.org/extend/plugins/buddypress-restrict-group-creation/ does this already.

You can set whatever defined wp_cap/role levels assigned to:
Create group capability
Create group forum capability
Create private group capability
Create hidden group capability

Read this:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/autocomplete-all-users-on-the-compose-screen

Hey hachimaki,

Your needs would need to be custom-coded. When a user creates a blog, they have the option to select its privacy. A possible solution involves checking if the blog in question is private; if so redirect to the registration page, if not, leave open to public.

Have you tried asking the plugin author?

i believe this will be fixed in 1.2.6

No idea ?

@linusf – Read the other solution Travel Junkie posted:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/?topic_page=3&num=15#post-44729

This will block everything but the register and activation pages.

@paul_gibbs we are also seeing issues using object-cache with BuddyPress and w3 total cache, most notably this manifests itself when trying to send Private Messages… We are using Minify, Database Cache, CDN (Amazon s3), and Browswer Cache (Developmental Version of Plugin)…

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/’ );