BuddyPress.org

I think I have this working, but came across a different issue preventing me from fully testing.

Here’s the code I was working with…

`

<label for="”>

<input type="text" name="” id=”” >`

Also, when I’m replacing `value=””` with `value=””` (using the correct field number) I’m blowing up registration.

Did that happen to you?

@xberserker — I’m looking for exactly the same thing.

Were you able to get it to not put the text above the field box?

@Shazar

Joining a site running Buddypress can be as simple or as convoluted as you want to make it for potential members. There are quite a few plugins that can be implemented for captchas; authentification via other networks like Facebook, Google, etc; profile synchronization with other networks; custom login pages and much more. An example of the basic BP account creation process can be found on one of my sites here: http://buddylite.com/register/

The only thing I’ve added to the default registration process on BuddyLite is a simple math captcha called Buddypress Humanity: https://buddypress.org/community/groups/buddypress-humanity/
You can see a working example of one front-end post solution called TDO-Mini-Forms on the same site here: http://buddylite.com/buddybuilder-style-submission/ and the end results here: http://buddylite.com/category/custom-buddybuilder-styles/
You’ll need to login as a test user to see the form though… user = buzzer / pass = hellobirdie

On another site I’m currently working on, you can see an example of another front-end post form called Quick Post Widget: https://wordpress.org/extend/plugins/quick-post-widget/
See it here: http://kwitterz.com/share-your-thoughts-with-all-kwitterz/
Again, you’ll need to login… user = pjohn / pass = gollysarge

Hope this helps to get you started!

I’d be interested if hearing if someone has figured out a way to use the Register Plus Redux plugin with BuddyPress…

website link?

works well for me
I would have loved to have a splitted registration form though (like fields from group1 on the 1st page, fields from group 2 & 3 on the following form registration page, etc), to prevent scare away users if you happen to have more fields you want them 2 fill in …

but I must be honest, I have NO clue as of how to achieve that ..

If you happen to find a solution, I’d appreciate if you’d post it back here

C.

I am posting this here because it might solve part of the problem and it worked for me: I found this <a href "https://buddypress.org/community/groups/buddypress-pending-activations/&quot; While it does not solve the issue of members being able to approve themselves, it does allow the ability to resend an activation link (email) and to manually approve members in the Que. It works with WP 3.1.3 and BP 1.2.8. I hope this helps the scores of people desperately seeking admin approval of new user registrations.

I found this <a href "https://buddypress.org/community/groups/buddypress-pending-activations/&quot; While it does not solve the issue of members being able to approve themselves, it does allow the ability to resend an activation link (email) and to manually approve members in the Que. It works with WP 3.1.3 and BP 1.2.8. I hope this helps the scores of people desperately seeking admin approval of new user registrations.

This seems to be a highly requested and necessary feature. Are there any plans for this type of admin control in future releases of BP?

== My new user registrations only appear in Network Admin -> Users. ==

Yeah, that’s how it’s done now since around WP 3.1 multisite, one is listed as user of a network – one login to all sites of multisite install as a subscriber (or role which the Super Admin set in options for new users).

This plugin could help with what you want to do https://wordpress.org/extend/plugins/multisite-user-management/

@gregfielding Doing `!bp_get_blog_signup_allowed()` isn’t probably the best approach though as it twists logic and if you did decide to close blog registration from the dashboard you would then be showing the form for blog signup the reverse of what you want.

Why not simply wrap the blog section in a test for a variable e.g:

‘$show_blog_signup = false;

if( $show_blog_signup) :

blog form stuff

endif;
`
Then you change the variable at top of page if needed.

It is

remove_action( ‘init’, ‘bp_core_wpsignup_redirect’ );

cool…thanks for reporting it back. I will try it out.

@gregfielding

Making it a custom page template and dropping in the entire register.php block didn’t work?

Also I’ve tried out the Gravity Forms add on for a registration form like this that can be placed in the page but I didn’t get into it much as I only tested it quickly when they introduced those addons. From what I recall it worked but something weird happened after the registration like the page not refreshing — I don’t remember. It also didn’t do what I wanted as far as no activation key and redirect to profile like what I use currently. So i shelf’d it. I think that would be a good option if you don’t mind getting GF. It’s a good investment! Actually, I think I’ll look into tinkering with it again.

`Warning: Cannot modify header information – headers already sent by (output started at /path/wordpress/wp-content/plugins/buddypress/bp-themes/bp-default/registration/activate.php:3) in /path/wordpress/wp-includes/pluggable.php on line 897`

As @r-a-y suggests, in my experience at least, that kind of error is almost always malformed PHP files — trailing spaces, unclosed brackets, stuff like that. If you’ve pasted functions into your functions.php or bp-custom.php, look there first, then any other template files you’ve edited.

“Update: Enabling the ‘Mail From’ plugin https://wordpress.org/extend/plugins/mail-from/ solves the problem.

I’m not thoroughly satisfied with this solution because it is too mysterious , but at least it is a solution.”

It’s not mysterious – it;s a symptom of exactly what I described. The hosts on the receiving end are killing the emails that are sent because they were *automated*. Changing the from address so it come from a “legit” email, instead of wordpress@yourdomain, made it so it got delivered.

Don’t use @r-a-y codes

@mikey3d – Is that a general recommendation?

I did say it was test code. Looks like you have whitespace issues in your /registration/activate.php. Delete any trailing whitespace from the beginning of that file.

eg.
`   -spaces – <?php` – Delete that trailing space!

Your htaccess rewrite rules look like it will interfere with querystring variables.
eg. example.com/my-page/?variable=my-test