We don’t even know if cookies are the issue.
His cookie domain info was set to “”. It’s not that it wasn’t set. It was set to null. So if wp gets to a spot where it wants to set it to a sane default value, it detects that it’s already set and doesn’t. Probably. The empty string is a value.
They would get loaded after the WPMU ones, so if there’s no check for them pre-existing, then they obviously overwrite them.
I currently don’t have a cookie_domain setup in wp-config.php either and everything works fine. It should get assigned by WPMU in wp-settings.php if it isn’t in the config.
In the wp-config.php file, verify:
$base = '/';
define('DOMAIN_CURRENT_SITE', 'domain.com' );
define('PATH_CURRENT_SITE', '/' );
define('SITE_ID_CURRENT_SITE', 1);
define('BLOGID_CURRENT_SITE', '1' );
…where domain.com is obviously your domain. If you are using any settings unlike what I posted above, paste them here please.
I wonder if the messaging system uses cookies?
It doesn’t sound really like the issue the 3 of us found. Does it? I just got finished working with somebody yesterday. His problem was that creating one group after another on the same computer caused the 2nd group to adopt the group id of the 1st group.
The underlying issue and solution was that he didn’t have any cookie domains set in wp-config.php
https://buddypress.org/forums/topic.php?id=3452
These cookie issues are tough to debug. We do the ‘works for me’ thing because our wpmu instances are different. Right now bp relies on the wpmu instance supplying the cookie path and domain. Perhaps to cover such situations bp should specify it’s path and domain. Would that bypass the wpmu credentials? Would it matter?
Here we go again. Burt, Jeff, man your battle stations. 
We’ll take a look at it.
Right now on testbp.org it looks like it’s working correctly. Was this an upgrade from a previous BuddyPress install, and if so, did you upgrade your member theme files also?
I just want to see if someone else can repro this before I open a bug in trac.
I am on WPMU2.7.1 and BP1.02. I have repro’d this on a 100% stock install using the default member theme.
Steps:
1. Browse to USER1’s profile page
2. Press “send message”, which opens compose message page with USER1 pre-populated in “to” line
3. Add USER2 manually to “to” line
4. Type a subject and message body
5. Press send
Result:
– Message is sent to USER1, but *not* to USER2
– Sent message page says “Sent between USER1 and admin.” – no mention of USER2
Strangely, using the skeleton member theme, I get the opposite (i.e. the message only goes to USER2).
Has anyone else seen this?
3125432Inactive
Ilya is correct about not having the ability to delegate.admin powers to a moderator. This is a very crucial issue. In a large community, people come and go. Their interests and time change. So say someone creates a group. They by default become an administrator. That means they are the only one to have the following powers in a group:
- Group Settings
Group Avatar
Manage Members (i.e. bump them to moderators)
Delete Group
So if we play out this scenario, and the administrator has fallen off the radar, the group settings from public to private to hidden cannot be changed except by the Buddypress site admin. The Buddypress site admin can elevate members to moderators but they CANNOT add an adminstrator, as far as I can determine. The Buddypress site admin can delete the group but the only way to “delegate” administrator powers would be to follow this scenario:
Appoint a moderator willing to take over. Have them create a new group, and then do a mass invite to join that new group via a news post or a friends invite.
Can a administrator be changed at the db level? Not sure.
What about asking the group administrator to exercise their option to ‘leave a group?’ I have no idea what that would do to the db and the Buddypress system. I’m hoping Andy or Jeff might chime in here on this odd possible outcome.
Cheers,
Brian
Is there a way to allow users to control the notifications they get in email. For example, if they would like to turn off the notifications that get sent when someone sends them a new private message.
I don’t see any mention of this in the forum or in Andy’s roadmap, but it seems like a feature that would be quite popular.
Dear Buddypress lovers,
Finally i am putting this as a project for all the developers out here. Please consider before giving any quotation that this project is being used for non profit community website and also will be donated to Buddy press community as an extension to buddypress.
I want to extend buddypress functionality for adding files for each user as his private files. Also In group It must be having a function to store its own files along with moderation from group administrator. (You can refer ELGG community software for its working and what i want)
As a developer myself i will be there with you on this project. But due to time lack i am not able to work on this project actively.
This project may require to hack buddypress core and database as well for storage of files.
Please let me know your thoughts on it.
Regards,
Sam.
One way off the top of my head would be to inject a JavaScript into the registration page – you’d use the BP name function to get what you want. There is already Wp code for “sanitizing” blog post names, and perhaps other areas too. Then it’s a matter of using the JavaScript to set the HTML field’s value, and CSS to hide it.
Thanks DJPaul! That sounds doable. Would it be possible to put that in a plugin or would it have to be inserted in core files?
Well, if you aren’t looking at how the underlying registration functions are coded, then how can you say with such certainty that this is not a WPMU issue?
What I need wouldn’t touch the underlying registration functions. All I need is another way to insert that username into the database on registration. Hiding a field on a form is basically an html/css issue, stuff that I know enough about.
Again, if the username would be generated from Buddypress’ required fullname field, it by definition is not a WPMU issue.
Also getting a more consistent connection in how Buddypress and WPMU handle first name + last name is not a WPMU issue; it’s about how Buddypress (x-profile) hooks into and synchronizes with WPMU.
WPMU does not allow you to position the username field in a different sequence–not without behind the scenes changes.
I have already done that once. It’s no problem. It’s annoying WPMU mixes presentation and functionality in the registration, but I’ll work with what I get.
Without contracting with a coder or coding yourself, you’re out of luck.
I am trying to code myself where I can and am certainly considering contracting a coder. I need to figure out what I need exactly first. Also with these posts I’m trying to point out some imho weaknesses in Buddypress that should get more attention and judging from the private comments I’ve received I’m not the only one struggling with these issues.
Yes, integration works fine between the two. It’s a private site, but I can PM you a login to use.
3314629Inactive
Hi everybody
Thank you for the replies. Unfortunately, as i mentioned, there isnt anything relevant in the buddypress submenu in wpmu.All i have is general settings, component setup and forums setup. And even in component setup, i dont have extended profiles, only activity streams, blog tracking, bbpress forums, friends, groups, private messaging. Why am i missing some of the fields you mention?I installed bp and wpmu 3 times already and its always the same.Are there some missing files or something?
Edit: yeah i went through and somehow i have missing files and directories. weird..
thanks
[I’m using WPMU 2.7.1 and BP 1.1]
I would like to display the thread title on the page that views a full private message thread. As far as I can tell, this should happen automatically, but on all the BP installations I have checked (including this one here at buddypress.org), the line “<h2 id=”message-subject”><?php echo $thread->subject; ?></h2>” in “messages_view_thread()” is not working, presumably because $thread->subject is an empty string.
I’ve searched, but no-one else seems to have brought this up. It seems so fundamental that I’m wondering what I am missing. Why are the thread titles AWOL?
My site is private and forces you to log on in order to see anything.
Is there a way to keep members out of regular behind-the-scenes admin areas entirely?
I had to request a new password for a test user. When you go through the process you’ll end up at a profile page in the admin area that is very different from the other profile editing options on the site.
The regular admin area doesn’t show X-profile data, so no full name, only that annoying username – I use the email login plugin. Of course the layout is very different, unless you go through the trouble of customizing the admin area to fit the front of the site.
What is Buddypress approach to this? Is it possible to completely close the back end for users? Will you cover all the account editing the user needs in the front of the site?
I found this plugin: Weasel’s Login Redirect, but it hasn’t been updated since 2007. This is what I need though:
Redirects user login attempts from going to your dashboard! Great for keeping the ‘back end’ private. Also allows alteration of the login/logout link text.
This one could be a solution: Peter’s Login Redirect. The name instills confidence.
3125432Inactive
I’m creating a slew of pages for our Buddypress installation that are all FAQ’s for the different functions. I highly recommend this to really understand the workings of Buddypress.
One of the draft questions I created was can a group admin change the access level to a different setting? Say it was private. Can they change it to public? Public to hidden? Hidden to private? And so on …
Another idea just hit me – a community depository of FAQ’s that admins can copy and paste into their pages or where they like. I am glad to get the ball rolling. Is there a way to share this with others?
Thanks,
Brian
I just recovered from a bad spam incident on my buddypress site. A user (who looked legit) suddenly started private messaging the whole community with obviously spam material resulting in some very angry members 
I will go ahead and install Akismet and a captcha during registration H.owever, is it true that each user has to obtain their own key from wordpress.com and plug it into Akismet to get it to work? Is there an alternative that I can just activate for everyone? Or can I just provide all my members with my key to activate their akismet?
Also, what steps have other BP admin used to prevent the kind of spam that I mentioned above? I do not think Akismet & the captcha during registration would have helped in this situation.
Is there a plugin that flags users who message a lot of users in a short time? Something like that might help fight spammers.
Thanks.
When I try to use the “Compose Message” page, I get an error in the drop-down box of the “Send To” field that reads:
Fatal error: Call to undefined function friends_search_friends() in (my URL)/wp-content/plugins/buddypress/bp-messages/bp-messages-ajax.php on line 33
I think this is due to the fact that I’m running a private install of BuddyPress where everyone knows everyone else already so I turned off friends. Is there a way to either fix this or at least remove the error? Messages are still sent properly when I type in the full username manually, but the error message is scary/distracting to my non-technical users, and when they click on it, it replaces whatever was already in the text field with “
“
Hi,
In our social network, groups represent real organizations and teams of people. We would like two things:
To be able to set the group as private ‘registration is limited to accepted membership requests’, but have the content and activity available to any member.
Also, we would like to introduce a new member type, ‘Fans’ – not group members as such, but people who want to be accociated with the group. For example, the British Red Cross set up a group, and their staff become ‘members’ of the group. People would become ‘fans’ or ‘followers’ of the group to show their respect to the group.
How would we go about these?
Many thanks
Thanks Mike,
I have been trying to figure out how to include that in the screen that comes up after a user enters their registration details and clicks next. Would you know what I have to edit?
Actually the problem is not only with activation emails..all emails generated by buddypress (alerts about private messages etc) seem to be going to the spam folders.
@P.S. The plugin looks good and how about adding a plugin forcing guest to register to view members & groups profiles ?
BuddyPress currently doesn’t support any kind of privacy control over profile data. Members of BuddyPress team are working on Privacy Component which will be part of some of the future releases, but until then this plugin can be helpful.
Xprofile Privacy plugin will give your users option to choose which profile data they want to share. Profile data can be public, viewable only to friends or be completely private. Users can set their privacy while editing profile or within Settings section in Profile Privacy part.
For more details, please visit:
http://devbox.computec.de/2009/06/buddypress-xprofile-privacy-plugin/
I created plugin that gives users option to choose which profile data they want to share. It is not exactly what you are looking for, but maybe it can help someone.
For details, please go to:
http://devbox.computec.de/2009/06/buddypress-xprofile-privacy-plugin/
Burt, I actually did try the first code you mentioned and of course, it did not work in bp-custom.php. I was actually going to post a reply to it, but you already did! Will test out the new code.
Thanks for your diligence!
—
John, one of the blogs in question would be the home blog, so we wouldn’t want to set that to “Private” and disallow search engines
But thanks for that little hint, might be useful in the future.
Cheers guys!
If a blog is listed as “Private” in the blog settings, that should also exclude it from the list. It will also exclude it from blog search engines and the like. Not sure how private you want this to be, but that’s about as private as it gets.