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.
I was thinking about doing something like this. Activity stream comments will create a corresponding blog comment / forum post and vice versa.
I think it’s possible, but there’s also the potential for problems to occur.
For example, someone replies from the activity stream at the same time as someone replying from the blog post.
Yeah, I amended my previous post after I typed it because I noticed the query would not work.
You’ll have to join the same table, then you could get the result you need.
Do a search on Google on self joins for more info.
I’m not a SQL guy myself, but because the data is divided in separate tables, look into constructing a select join query.
See how it’s done in /bp-xprofile/bp-xprofile-classes.php
Actually it is possible to bypass BP registration using the wp_insert_user() function.
It *should* be possible by overriding the /registration/register.php template file in your child theme. But all the good stuff like activating an account would be gone. However, you say you want to use WP’s registration system? Would require a BP core hack I believe.
Changing the BP_ROOT_BLOG wouldn’t do a thing since BP is activated network-wide.
Hi Andrea, this isn’t true. A bug was fixed a few weeks ago in bp-blogs-classes.php that wasn’t correctly pulling a user’s blogs.
@hnla – Just for sanity’s sake, I tried again. This time via “Super Admin > Blogs”. I clicked “Edit”, then added an existing user to the sub-blog that way. Works. Can you check to see your wp_bp_user_blogs table to see if it’s recording anything?
I noticed with database caching on in W3 Total Cache that if someone registered on a BP site, two additional accounts would be created with the same username, but their user ID for each of these new accounts would be different. So unfortunately I had to disable database caching.
Haven’t tried W3 Total Cache 0.9 to see if this is fixed.
Instead of re-enabling the admin bar every time, why don’t you just use this xprofile_setup_adminbar_menu() somewhere in your theme?
Make sure you wrap [ul] around the function though.
Either that, or enable the BuddyBar for admins only.
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!
