User and avatar information is stored in wp_signups before the account is activated, and it is moved into the user, usermeta, and xprofile tables upon activation.
It would seem you’re experiencing a different issue than what you describe.
For now I’m closing this and linking it to…
https://buddypress.org/forums/topic/avatar-upload-issues?replies=1#post-28737
@titeufpld, if you’d like me to reopen this topic for some reason, send me a PM.
It’s a good idea and one I’ve tossed around, but the problem is that it would need to exist outside of the wp-content/buddypress/ directory to avoid automatic update problems, and people wiping out the plugins folder on accident (if they do a manual upgrade for example.)
Something like this may still happen down the road, as BuddyPress grows and a need for specific methods to register plugins with BuddyPress increases. At the moment it isn’t necessary because BuddyPress plugins are actually just normal WordPress plugins that may take advantage of BuddyPress features and API’s. (At least, that’s how plugin authors should be writing them.)
What will need to happen for sure is a way for plugins to tell BuddyPress “hey I’m here and I want you to know this information.” It’s possible to alter the $bp global directly to do these things, but tighter integration into the platform makes sense.
My opinions are subject to change on this one, but today that’s how I’m feeling.
I’m wanting to create a few special forums on our site that might go beyond the basics offered with buddypress.
I want to create a group that only members can post to, but anyone can view. this is between public and private. Is this possible?
Also, I want to create a group that will act more like a announcement list, where many people can join but only an admin can post to it.
any idea if that is possible, and if not, how I should go about doing it.
Hi all
I’m trying to get a pop up to work so that when you click on ‘Cancel friendship’ button, it asks you if you’re sure first.
This is the code that controls the cancel function:
echo 'loggedin_user->domain . $bp->friends->slug . '/remove-friend/' . $potential_friend_id, 'friends_remove_friend' ) . '" title="' . __('Cancel Friendship', 'buddypress') . '" id="friend-' . $potential_friend_id . '" rel="remove" class="remove" onclick=" confirmSubmit(); return false;">' . __('Disconnect', 'buddypress') . '';
This is from the bp-friends-templatetags.php file, you can see the ‘onclick’ command I have added.
This is what I have in the head:
<script LANGUAGE="JavaScript">
<!--
function confirmSubmit()
{
var agree=confirm("Are you sure you wish to disconnect from this member?");
if (agree)
return true ;
else
return false ;
}
</script>
It works, but pressing the ‘cancel’ on the pop doesn’t, it just cancels the friend anyway.
Has anyone got any ideas please?
Thanks very much
Devweb
5339130Inactive
After uploading the themes to the server, they were available in “apearence” I selected and activated. Then I went to site admin -> themes and clicked on “Yes” on Avenue K9. The I did F5 on another FF tab to see how it did looked like, and got a blank page. The themes working at the moment are BuddyPress Default, BuddyPress Social Network Parent Theme and those that come as default on wordpress.
No code was modified
i have a buddypress/mu install that i’m working on that i could use a little help.
when a user logs in the plugin checks to see if they are in our database and if the password is good or not. If it is, it automatically creates the user into wordpress using their email, username and password.
The problem i’m having is when i create their blog with
wpmu_create_blog($domain, $path, $title, $user_id, $meta, $site_id);
it creates the blog, usernamexxx.domain.com but doesn’t have any styling to it and says
Error 404 – Not Found
Am i missing something?!
Anonymous User 96400Inactive
This is being handled with functions like these:
bp_core_new_nav_item
bp_core_new_subnav_item
bp_core_remove_nav_item
bp_core_remove_subnav_item
All of these functions (and a lot more) can be found in buddypress/bp-core.php. They are well documented and you can always have a look at the various core component how they use these functions.
To the admin bar you can add links like so:
function sv_add_link()
{
global $bp;
$link = '<li><a href="'. $bp->loggedin_user->domain . 'my-page" title="'. __( 'My Page') .'">'. __( 'My Page') .'</a></li>';
echo $link;
}
}
add_action( 'bp_adminbar_menus', 'sv_add_link' );
Removing links also works with actions. Using the example from above you’d have to put this into your functions.php file:
remove_action( 'bp_adminbar_menus', 'sv_add_link' )
You have to remove an action at the same priority as it has been added, so if you find an add_action call like this:
add_action( 'bp_adminbar_menus', 'sv_add_link' , 7 );
you’d have to remove it with this:
remove_action( 'bp_adminbar_menus', 'sv_add_link' , 7 );
Otherwise it won’t work.
Hope this helps you along a bit.
5339130Inactive
I’m using the latest version available on site to download WordPress MU and buddypress.
WordPress MU 2.8.5.2
Buddypress 1.1.2
When users upload a image at signup it shows up as a brokern image on theyre memberpage. Here is the img-tag:
<img src=” alt=’Avatar Image’ id=’user-1318-avatar’ class=’avatar’ width=”50″ height=”50″ />
I can see that the “src” in the tag is missing, anyone know why?
Can anybody help with this issue?
I have the latest WPMU version (2.8.5.2) and buddypress 1.1.2 installed
Same problem,started about a few days ago. Bots are signing up a few times a day, firstnamelastname19xx.
Interesting is that I notice in my stats some ip found my site by searching for “proudly powered by WordPress MU and BuddyPress”.That could be a reason that this particular bot is finding and attacking bussypress installs.
If this bot is getting past Captcha, I would recommend applying a reverse Captcha technique. Just do a bit of Googling on this, it uses a hidden field as a honey pot which bots will fill in, but normal users will not. When filled in you can redirect them to a page of your choosing.
Please report your findings and how you deal with this as it would be very helpful.
OK, so I used the code from Xevo in this thread in a custom functions.php in my child theme. It redirects all calls throughout all the WPMU blogs to signup.php to the BP register page, which should help you do what you want, if I understand correctly.
One thing this hack doesn’t do is to pick up any changes to the register slug in wp-config, though, so you’ve got to remember that if you change it.
We have moved our buddypress home page to a fixed static page via dashboard > reading. We have customized home.php so everything shows up as it normally would without using a static front page except that the loop does not show, it doesn’t seem to recognize that this is where posts are meant to show up.
In the past we had to delete a line or two from functions.php but now the functions are different and we haven’t been able to make any tweaks that have worked.
Anyone know how to help BP recognize the loop on a static post page? Any feedback appreciated!
Just updated to WPMU 2.8.5.2 from 2.8.4a, updated BP to Buddypress Trunk 2087. With the only plugin active BuddyPress, the gray admin bar “My Blogs” menu is missing Blog ID#1 for all users. Have exhausted myself re-installing etc etc same results.
Also, when I click on “My Blogs” main menu button in the gray admin bar, or “Blogs” in the gray admin bar “My Account>Blogs” or from my profile left sidebar menu “Blogs” I get this:
Fatal error: Cannot use object of type stdClass as array in /home/copgarde/public_html/wp-content/plugins/buddypress/bp-blogs/bp-blogs-templatetags.php on line 367
Anyone have any ideas what I can do to fix this?
Hi,
I was cleaning up my WPMU/BuddyPress install today and somehow caused none of the main tabbed links (“Blog”, “Members”, “Groups”, “Forums”, and “Blogs”, specifically) to work for any blog other than the main blog directory (for which the links work fine).
I think this may have happened because I was deleting theme folders I thought were unused. At this moment, I only have the following two theme folders within /wp-content/themes/ :
bp-default, and
bp-sn-parent
Obviously, bp-default is the one that is activated (my only choice).
I have tried deactivating and reactivating this theme, as well as deactivating and reactivating the entire BuddyPress plugin, but I still get the message “The page you were looking for was not found.”
Does anyone know why the aforementioned links give this error message for all blogs except the main blog?
Thanks in advance for help!
I have never received any answer on teh original questions and I am getting really tired of deleting the splogs that happened only after installing Buddypress.
Just the last few hours 5 splogs registered, all with name-surname19xx as username, all from different email domains.
I know it is not too much to check every blog, check every user, mark him as a spammer and add the email domain to the sh*tlist under options.
But the point is that before BP I had to do this less than once per month. So I repeat, hopefully somebody wil;l at least answer the2nd question (hopefully the first as well, but I fear a standard ‘ask the plugin-author’ reply):
“So my questions to determine the best action to make sign ups easy but splogs difficult:
– why won’t the WPMU sign-up question plugin work on the BP register page? Is there a way to fix that?
– More importantly: Can the register page be renamed? If so, which file(s) and what other (internal) links?”
Many thanks,
Cheers, Harry
I just basically opened my new site to signups, and I’ve been getting a couple of signups a day, but I’ve just realized they’re more than a little suspicious. The tip-off was that the ‘Where are you from?’ basic profile field required on my /register form was gibberish for all of them (yeah, I know, should have been obvious, but). Everyone of the usernames are reasonable given name/surname combinations with a year tacked on the end, as well, like derrickthornton1983 and so on.
Damn it.
The weird thing is that one of those accounts seems to have successfully posted a blog post, which scares me if it’s a bot. And confuses me, too — I had no idea that that level of sophistication might be possible. Here’s the link: http://jobsee.kr/community/juliedecholet/2009/11/12/depuis-le-temps-voil-ma-page-personnelle/
Note that the useraccount name is derrickthornton1952 on BP, the site URL is juliedecholet, and the ‘post’ is signed Jessica. Pretty certain this is spam of some kind.
So, are you folks having the same problems? Does your spam look like this, too? What do you reckon is the best way to choke it off? Could you tell me (and us) about your experiences? I wonder how this site itself deals with the issue — I assume as the oldest Buddypress install (and the one at testbp.org) it must be hit the hardest.
I am running buddypress 1.1.2
Viewing the code I downloaded for buddypress downloads.wordpress.org, if you start at line 236 is the only place the word public appears… the code is still the same:
function bp_field_has_public_data() {
global $profile_template;
if ( $profile_template->field_has_data )
return true;
return false;
}
andrepan and levin, please also check out other multi byte issues. You two seem to be fluent in programming, perhaps you can solve them. 
https://buddypress.org/forums/topic/buddypress-i18n-topics
This is more a limitation of WPMU than it is a core BuddyPress feature. This could also easily be addressed in a plugin.
I’ll take a look at #1251 soon…
@MrMaz
Ah, that’ll be it. Just found out my host is running php 4.4.8. I’ve another server running php 5.2.6, I’ll move everything accross.
Thanks for you help.
Found the buggy lines, kind of weird because poEdit said that I was done translating. Anyway, edited them and now I can easily open it.
Now just finding out why buddypress doesnt copy the wpmu language setting.
Part of the problem could be that the textdomain is set to ‘buddypress’ for all links in the filters.
ucwords( __( $component_name, 'buddypress' ) )
..so if your plugin uses its own textdomain everywhere AND needs to tap into this list, it will need to use the ‘buddypress’ textdomain somewhere too.