BuddyPress.org

I use https://buddypress.org/community/groups/wp-fb-autoconnect/ premium version. Its developer has automatic profile fields population in his roadmap, but with no release date unfortunately

very cool plans and plugin! u know, i’m also now trying to build smth. described by u and not sure if it’ll be possible.

for example, i want to use this native FB registration plugin
http://developers.facebook.com/docs/plugins/registration

but have no idea how to implement it

well, that (velomash) will not help much unfortunatelly .. nor will the required fields be cheked or the information for all group fields saved to the database!
Buddypress is so damn buggy on this one, wonder if they really thought of the purpose of implementing those fileds without proper connection to teh registration form; who the h* (sorry!) will go to fill in the fields if not requested upon registration?

dont worry, 2 years latert the sh* is in the same stage

I think it will be easier a plugin that :

1) Lock Buddypress to non registred users
2) Allow to configure the welcome page as facebook does, with login area for registred, and register fields for non members and backgrounds, info, links on this welcome page.
3) After the register process, show a page to upload avatar or skip this step.

@4ella Yep. I’m having the same issue

Does anybody else has a problem with avatar upload after succesful registration ? My new members succesfully sign up and then succesfully upload their photos , then they go to their email accounts to activate it and when they come back into their profiles their uploaded profile photo is not there , so they need to upload it again – this time without any problem , obviously many of them let that be , pls where should be a problem ?

here’s my workaround for this problem

https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/multiple-profile-group-fields-in-registration/?_wpnonce=98e520cdd5#post-98202

as no buddypress gurus EVER botherd to give a feedback on this, and left everyone here in the dark for more than 1 year

the above still sucks of course (or rather the whole registration process for buddypress sucks!), anyway, the above code will unfortunatelly NOT validate the fields! So it would be possible for a user to register without filling those fields in …

Yeah, you tell me how happy I was as I realized that!
1 more day lost with this s*, but eventually found a workaround (I am sure it’s not the perfect solution, but at least it’s SOMETHING!)

So in order to have the required fields really checked, please add this to your header:

`

$(document).ready(function() {
$(“#signup_form”).validate();
});

`
where signup_form is the id of your form (

hmm … I am afraid that plugin does smth. else, namely automatically registering a new user to a group, but what we meant here were the registration fields from xprofile.

Actually, I figured out a way to have them displayed, although there’s a lot of css fun you’ll have afterwords

In register.php you should look for this
“

and replace with this
“

This will display all the fields, but you’ll still miss the Title of each group.

To get that displayed, you can do this:

Look for
“

and just above it place this: `

`

That should do the trick.

It’s a dirty hack from a no-programmer, so please do not criticize. As anyone can notice, no programmer / developer ever cared to offer any help with this.
Actually very annoying that no one frm the development team ever thought about it, leave alone giving a hand here …

Hope you’ll find the trick useful though

I think this should help https://buddypress.org/community/groups/buddypress-registration-groups-1/

ok, so it seems that “tomorrow” never happened

Anyone who found a solution?

Anyone managed to come up with a solution to this?
It’s a bit lack of logic to allow fields to be set as required in the backend but never show them to the user when registering … what kind of required fields are they than?

Thank you!

I have the same problem – latest BP / WP (3.1.2) versions installed. Fact is that in the buddypress “Profile Field Setup” you are allowed to create different groups of fields and set for each field if it’s required or not.
BUT, all fields other than those from the 1st group are NOT considered in the registration process!
The email is apparently sent once the user completed only the 1 step, and it just stops after asking the user to upload a photo.

So basically, the extra group fields (no matter how “required” they might be) are fully IGNOFRED in the registration process!

Anyone please help?
This is a buggy

Thank you!

Taken from bp-default 1.3:

`
<?php
/*
* Template Name: One column, no sidebar
*
* A custom page template without sidebar.
*
* @package BuddyPress
* @subpackage BP_Default
* removed since notice hnla
*/

get_header() ?>

`
Not sure if this is practical as it is from 1.3 but the principle is sound. You would need to ensure your custom markup – if any – was replicated in this page and change the top template notice to 1..28 this would then give you a selectable template for when you create any pages that don’t require sidebars. When 1.3 lands live you will also be able to use templates for regular BP pages such as registration as 1.3 uses pages for the main components.

thanks so much, the above approach worked, Am using a child theme created by me, but i copied all the files from bp-default theme and customised it. where can i get the onecolumn-page.php template? am not developer but its only help from people like that push me this far

regards

Yes and no, you would need to change the body class token body.register is particular to the registration page so you would need to do something like:
`
body.page-id-1215 #content,
body.register div#content {
margin-right:0;
padding:0;
width:100%;
}

`
page-id-1215 is the only unique identifier of that page.

However this approach isn’t really the best one, it would be better to be using a onecolumn-page.php template that has the sidebar removed as is provided in the bp-default theme then you would select that page template for you terms&conditions page and when 1.3 hits you would do the same for the registration page.

thanks hnla you are a star, it worked like a charm. one more question, can i use this code to remove sidebar from a page aswell. for example, “Terms of service”

`body.register div#content {
margin-right:0;
padding:0;
width:100%;
}
`

hi, i just follow this instruction using option 1 i put this code in my style.css

body.registration #sidebar { display: none; }
body.registration div#content div.padder { margin-right: 0px; border-right: none; }

and it worked, but how can i set the form to full page or make it center.

see here ; http://www.naijaping.com/register/

regards

I haven’t really explored it much, apart from getting the css to match various site designs…. I’ve tried to avoid using it but the spam (particularly the spam registrations) gets to be annoying. Adding this and the problem goes – apart from what appears to be the odd human spammer…

You could change where it says CAPTCHA Code to your own message – It’s an option at the bottom of the admin screen.

It would be nice to be able to place a text line above the graphic and above the captcha code line….

BuddyPress doesn’t interfere with user registration at that level. I think you’re almost certainly doing something wrong if you are needing to create your own hash for the password, etc. The authentication class is overridable, and most stuff can be done via the ‘authenticate’ action (I think that’s the name). I would rethink the approach you are taking, and do a bit more research — the wordpress.org forums may have had discussion about hooking into the registration process, and certainly the codex does.

Not choosing sites from signup process, but after registrations, you can place this widget to the sidebar of a site so as to users can register with that site.

https://wordpress.org/extend/plugins/add-users-sidebar-widget/

Wonderful, Tom. A minor tweak to your solution:

The original remove_action may not always work
remove_action( ‘bp_adminbar_menus’, ‘bp_adminbar_login_menu’, 2 );
since we can’t guarantee that buddypress plugin is parsed before this fix plugin. A slight modification I made works for me:

I change add_action( 'bp_adminbar_menus', 'custom_bp_adminbar_login_menu', 2 );
to
add_action( 'bp_adminbar_menus', 'custom_bp_adminbar_login_menu', 1 );
so it will run before the original bp_adminbar_login_menu runs, but after the plugins are parsed and hooks are registered, and then in custom_bp_adminbar_login_menu, I added
remove_action( 'bp_adminbar_menus', 'bp_adminbar_login_menu', 2 );

Therefore, the whole thing looks like:

function custom_bp_adminbar_login_menu() {
global $bp;

remove_action( 'bp_adminbar_menus', 'bp_adminbar_login_menu', 2 );

if ( is_user_logged_in() )
return false;

$redirecturl = $bp->root_domain . '/wp-login.php?redirect_to=' . urlencode( $bp->root_domain ) . esc_url( $_SERVER );
echo '
' . __( 'Log In', 'buddypress' ) . '

';

// Show “Sign Up” link if user registrations are allowed
if ( bp_get_signup_allowed() ) {
echo '
' . __( 'Sign Up', 'buddypress' ) . '

';
}
}
add_action( 'bp_adminbar_menus', 'custom_bp_adminbar_login_menu', 1 );

I agree with fbutera101, though — I am having a hard time imagining a use case where users want to leave where they already are after logging in.