could you be a bit more specific, there was nothing there that i was specifically asking for..
You can find the plugins here http://wpmudev.org/
Okay great i saw your registration this morning, and i found footer called for twice template, but why does edit profile not work, it says that group does not exist??
my wpmu/buddypress is on the root, but my registration page returns 404 as well. However if I manually type wp-signup.php, then it shows the page just fine.
Robust classifieds (paid and free)
Group calendar/events with registration
Photo galleries (for groups, members, and group events)
Cheers!
?Participant
BuddyPress is to build a social network! For a newspaper you can use a simple CMS.
That drupal module looks strong, it has a lot of interaction with Picasa! However, I think photo galleries in a social network are more like a way to share moments rather than a tool to showcase personal work or store/backup images.
Personally, when I use the photo galleries at Facebook with my friends is to share photos related to something specific (a party, meeting, birthday, old photos from school, etc). They have enough quality to be downloaded (but they won’t be useful if you want to work with them later).
Using a third party service like Picasa or Flickr makes your site depend on other site to work, and forces your users to open an account on any of those services (users don’t like registrations, and even sometimes they don’t know how to link one account with other). I know this won’t be an issue for the average person in this forum, but future potential users will have problems, and we have to think every single thing to be as fool-proof as possible.
If you are concerned about storage, maybe you can use a professional service then (like Amazon S3). But if it’s about privacy then it would be better if you don’t host photo galleries at all. Privacy is another thing that needs to be reviewed at BuddyPress!
It must be because you are running an older version of BP alunsina. Sign up goes to the registration form. What happens when you upgrade BP? White screen of death? There have been lots of changes recently including changes to the directory structure for the member themes. See: https://buddypress.org/forums/topic.php?id=1675
That was effective rev 1211. Make sure you update the member and home themes also. Lots of changes in the security area from wpmu 2.6 to 2.7.
When you upgrade to the latest bp what do the apache error logs say? That’s the only way to find out what is going wrong. White screen of death means that a fatal php error is happening.
You should write a function that adds user to a group (using the bp-groups functions) and add it via add_action to the registration process
i don’t know if the ID of the user is in $bp->loggedin_user->id while the user has activated the new account
Thank you. I sent a support ticket to my server/host. Seems to have been fixed now.
bp doesn’t control how or if registration emails are sent. It relies on wp to do that. It depends on your host and if you have wpmu configured properly. I signed up with your site and didn’t get an email either. So it’s not just you. Try the wpmu forums for help. https://mu.wordpress.org/forums/
Hi all,
i had the very same problem at http://buzzdev.org that default role on main blog was ignored for new user signups.
I am running plain WPMU 2.7
Looked into the source code and solved the problem by editing wpmu-functions.php at line 672 (function “add_user_to_blog”):
//$user->set_role($role);
$user->set_role(get_option("default_role"));
Now whatever default_role i set in wpmu/options.php it gets applied to new user registrations.
take care
buzz
http://buzzdev.net
http://buzzdev.org (wpmu test)
I fixed it:
at the end of buddypress-home/comments.php I changed:
</form>
</div>
<?php endif; // If registration required and not logged in ?>
<?php endif; // if you delete this the sky will fall on your head ?>
to:
</form>
<?php endif; // If registration required and not logged in ?>
</div>
<?php endif; // if you delete this the sky will fall on your head ?>
Is this still working for everyone else?
I’m using BP trunk and, although the option for default friend appears in my admin section, the default friend is no longer being added upon new user registration.
I see, I see… thanks
by “make plugin” you mean just handcode what i want….
can you tell me which files to edit:
wp-signup.php
(edit this to add extra fields to registration once I remove x_profile functionality)
how about the “edit profile” page?
which PHP file is that?
I still need to display those fields as “readonly”
thanks again
To do this you’ll have to replace the current bp function xprofile_add_signup_fields() with your own. In bp-custom.php create a new function that renames the current function like so. Just copy the whole thing over and rename it.
function my_xprofile_add_signup_fields(){
<body of existing bp function>
<your mods to the avatar area>
}
remove_action( ‘signup_extra_fields’, ‘xprofile_add_signup_fields’ );
add_action( ‘signup_extra_fields’, ‘my_xprofile_add_signup_fields’ );
Avatars are created by the xprofile component as part of the ‘signup_extra_fields’ action, specifically bp-xprofile-signup.php.
My guess is you could create your own action and add it to ‘signup_extra_fields’ and remove the ‘xprofile_add_signup_fields’. I say guess as I have not tried it 
.
i hope to have understood: should not you simply add the day and month to the custom field of your registration page? it is allowed from the back end of buddypress and these data are shown in profile pages.
How can I hook bp_show_blog_signup_form() or bp_create_blog_link or other related function?
I want it not to show registration blog content. I mean when user “has limited his numbers of blogs per member” there is no link to create a blog.
Or even better: There is a link, but without blog signup form, but with the message: ‘Limit nine blogs per member. If you would like another, please contact an Admin for assistance.’
I do not want to hard coding in member-themes’ files. I’m creating a plugin with Admin page to configure this.
J, thanks for the suggestion, but unfortunately that just takes you back to the registration page.
I’m thinking along the lines of using the predefined ‘user_name’ which identifies the user, then the activation key is ‘activation_key’ in the MySQL DB. I need to use the ‘user_name’ to call the equivalent activation key and I think ‘&_GET’ to the activation page by having the activation key placed into a url.
Anyone have any idea how to do this or have any suggestions?
Cheers all
I would do this by going into /member-themes/buddypress-member/blogs/create.php and doing…
<?php if ( bp_blog_signup_enabled() ) : ?>
<?php
global $bp;
$blogs = bp_blogs_get_blogs_for_user($bp->loggedin_user->id);
if ($blogs['count'] != 9)
{
bp_show_blog_signup_form();
}
else
{
?>
<div id="message" class="info">
<?php _e( 'Limit nine blogs per member. If you would like another, please contact an Admin for assistance.', 'buddypress' ); ?>
</div>
<?php
}
?>
<?php else: ?>
<div id="message" class="info">
<?php _e( 'Blog registration is currently disabled', 'buddypress' ); ?>
</div>
<?php endif; ?>
Just remember not to overwrite the member theme if you do a BuddyPress update. 
None at all. The blogs ability you can turn off and on as you’d like, even on a whim.
You’re exactly right. Turning off blog registration only disallows new blogs to be made when registering and by currently registered users. As a site admin you can still create new blogs and even assign blogs to individual users. The backend is still open to you, but not to other non-admins.
Just out of curiosity, are there any consequences to be aware of if I choose to launch without blogs initially, and then allow my users to create them in the future? For my particular target I like the idea of having a guaranteed new feature release in my pocket.
Also, what happens to existing blogs if you turn off blog registrations? I assume nothing and that the admin can still create blogs. Just looking for a confirmation on that.
Well, if I understand correctly it certainly seems possible, considering its pretty much the way that WordPress installation goes.
You install WordPress and are provided a login (“admin”) and a randomized password.
If you’re looking for code to try to tap into, or an example of how to go about it, that would be where I would look first?
The next step in your theory would be to consider how to handle spam registrations in the event that user never sees the pw and never logs in to your website. Maybe take a look at the Register Plus plugin for WordPress.org to get some ideas also?
Bigkill,
glad to see that it’s working (although not as secure as you thought) as i understood it, you have to force it sitewide because the registration page is for your whole site, not just the main one.
As far as wp-recapatcha not being the best, well this might be the case, but it does prevent some spammers. I was having a problem with scripts bypassing the entire registration process and starting up profiles and blogs without entering any of the required fields, and the only way i got them to stop, was to change my “wp-signup.php” to something different like “sbn-start.php” and replaced the 4 instances of it in the “wp-signup.php” file with “sbn-start.php” and then went into “bp-core-template-tags.php” and replaced the one instance of “wp-signup.php”.
This solved the problem (crossing fingers), but I still have a few people getting by that I have to manually spam and ban, but I can deal with 2-3 a day versus waking up in the morning and finding 200 spam blogs signup over night.
Hope I helped.
