BuddyPress.org

I have the same problem. I used the bp-default and created a child theme named default and put it under the themes directory. I did this to replace the original default theme. I was hoping that when new users create an account they would assume the child default theme automatically, however, I noticed when test creating blogs that they don’t work at all since 1.2 buddypress. I deleted my original default theme and all 100 blogs are broken now. Will you have a fix for this soon?

error for new blogs:

The blog you have requested is not installed properly. Please contact the system administrator.

old blogs will not connect to new default child theme?

Thanks

I know you’ve solved the problem but I recently used this as a solution, this code removes the Blogs button from both your “My Account” menu in the admin bar, and the Blogs button in your profile navigation.

Put this code in your bp-custom.php file:

function remove_blog_buttons(){

remove_action( 'bp_setup_nav', 'bp_blogs_setup_nav' );

remove_action( 'admin_menu', 'bp_blogs_setup_nav' );

}

add_action('plugins_loaded','remove_blog_buttons');

I hope this helps

Same issue here. Set it up and created a test account but no email was sent.

WP 2.9.2 and BP 1.2

Also, I needed to edit the plugin to allow up to 1000 listed in the message from pulldown so that I could select my user account.

Thanks!!

IF: >> wp-admin >> Site Admin >> Options >> Allow new registrations >> Only user account can be created

is chosen, you can not have blogs, the logic stand… this is a little flaw in WPMU, not buddypress… this will be corrected with WP3.0

in your plugins folder (if you don’t already have one created) create a file called bp-custom.php

within that file put:

<?php



function new_search_action() {

global $bp;



return apply_filters( 'new_search_action', $bp->root_domain . '/search' );

}



function custom_adminbar_search() {

$mobSearch = '

<li class="align-right"><form  action="' . new_search_action() . '" method="post" id="search-form">

<input type="text" id="search-terms" name="search-terms" value="" />

<input type="submit" name="search-submit" id="search-submit" value="" />



' . bp_search_form_type_select() . '



' . wp_nonce_field( 'bp_search_form' ) . '

</form></li>

';



echo apply_filters( 'bp_search_form', $mobSearch );

}

add_action('bp_adminbar_menus', 'custom_adminbar_search', 100);



?>

This will get your search to the top, and placed on top of your “visit” button. If you get rid of the class="align-right" in the list tag, then it’ll put it beside the notification button. You’ll notice that things seem a little screwy when you scale the page, so you’ll need to play around with putting a div around it etc etc. But at least this’ll get it up there for you.

To remove items from your admin bar:

function modify_adminbar(){

remove_action( 'bp_adminbar_logo', 'bp_adminbar_logo' );

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

remove_action( 'bp_adminbar_menus', 'bp_adminbar_account_menu', 4 );

remove_action( 'bp_adminbar_menus', 'bp_adminbar_blogs_menu', 6 );

remove_action( 'bp_adminbar_menus', 'bp_adminbar_notifications_menu', 8 );

remove_action( 'bp_adminbar_menus', 'bp_adminbar_authors_menu', 12 );

remove_action( 'bp_adminbar_menus', 'bp_adminbar_random_menu', 100 );

}

add_action('plugins_loaded','modify_adminbar',99);

This removes ALL of the previous functions, so lets say you want to remove.. the visit button:

function modify_adminbar(){

remove_action( 'bp_adminbar_menus', 'bp_adminbar_random_menu', 100 );

}

add_action('plugins_loaded','modify_adminbar',99);

And there you go. Hope that helped.

You can change your registration slug by adding this to your wp-config.php file (above the stop editing line):

define( "BP_REGISTER_SLUG", "create-an-account" );

You can then happily upgrade without worrying if it will break.

Reference:

https://codex.buddypress.org/how-to-guides/changing-internal-configuration-settings/

I have adjusted the wp-hashcash plugin to work with buddypress signup. Here is what I did: I got the wp-hashcash plugin and I added the following code to the file:

global $bp;

// get our options
$options = wphc_option();
$spam = false;
//if( !strpos( $_SERVER[ ‘PHP_SELF’ ], ‘wp-signup.php’ ) )
//return $result;

// Check the wphc values against the last five keys
$spam = !in_array($_POST[“wphc_value”], $options[‘key’]);

if($spam){
$options[‘signups-spam’] = ((int) $options[‘signups-spam’]) + 1;
wphc_option($options);
$bp->signup->errors[‘spam’] = __(‘You did not pass a spam check. Please enable JavaScript in your browser.’);
} else {
$options[‘signups-ham’] = ((int) $options[‘signups-ham’]) + 1;
wphc_option($options);
}

}
add_action( ‘bp_signup_validate’, ‘wphc_check_signup_for_bp’);

function wphc_error_hook_register_page(){

do_action(‘bp_spam_errors’);

}
add_action(‘bp_before_register_page’, ‘wphc_error_hook_register_page’);

Then, under the line (line number about 507)

I put this line:

Then I activate the plugin. It should keep spam bots from being able to create accounts, but humans spammers can still do it. Anyway, if you can’t get it to work, let me know via PM and I will try to send you the file.

Later

If you have Cpanel yo can use this code for activate external mail for yours users

http://www.zubrag.com/scripts/cpanel-create-email-account.php

… if the current interface is not intuitive enough then no matter how many screencasts are created users will still be confused.

Absolutely agree. You should not have to educate users how to use your site. Please, if you have time to spare, use it to help improve the user interface instead of making videos.

Also a clear explanation to the users between their buddypress profile and blog dashboard would be nice!

How about closing the blog dashboard to members and bringing the functionality into the Buddypress profile, under Settings or Account, under the site’s theme?

I’ll have to figure that one out when I have the time…

@mike

i installed David’s chat plugin on the FR demo site http://buddypress-fr.net/bpdemo/

(wp 2.9.1.1 & bp 1.1.3)

Feel free to create your account and test it !

1) https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/

2) Go to your wp-admin area, in the BuddyPress menu go to “Component Setup”. This lets you disable/enable each component of BuddyPress. If you disable, they are removed from menus. If you want the component active but not on your menu, you will need to create a child theme: https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

@Bowe

setting up different group types is fairly easy. You just have to attach some groupmeta to the group, that basically let you add as many types as you’d like. Then you just check the metadata to figure out what type of group you’re in. Using the groups API you can then add different functionality for different groups.

I’ve written a types-plugin for one of my sites. It doesn’t have an interface, though. The 3 types I needed are hardcoded into it, so it’s really not suited for a release at the moment. There’s also a lot of more stuff, like a shopping cart, part of that plugin. So, I’ve stripped the functions needed for group types out (hopefully al of them).

First we need to add the addtional fields to our registration form:

function sv_add_registration_group_types()

{

?>

<div id="account-type" class="register-section">

<h3 class="transform"><?php _e( 'Choose your account type (required)', 'group-types' ) ?></h3>



<script type="text/javascript" defer="defer">

jQuery(document).ready(function(){

jQuery("#account-type-normal_user").attr("checked", true);

jQuery("#group-details").hide();

jQuery("#account-type-type_one,#account-type-type_two,#account-type-type_three").click(function(){

if (jQuery(this).is(":checked")) {

jQuery("#group-details").slideDown("slow");

} else {

jQuery("#group-details").slideUp("slow");

}

});

jQuery("#account-type-normal_user").click(function(){

if (jQuery(this).is(":checked")) {

jQuery("#group-details").slideUp("slow");

} else {

jQuery("#group-details").slideDown("slow");

}

});

});

</script>



<?php do_action( 'bp_account_type_errors' ) ?>

<label><input type="radio" name="account_type" id="account-type-normal_user" value="normal_user" checked="checked" /><?php _e( 'User', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_one" value="type_one" /><?php _e( 'Type 1', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_two" value="type_two" /><?php _e( 'Type 2', 'group-types' ) ?></label>

<label><input type="radio" name="account_type" id="account-type-type_three" value="type_three" /><?php _e( 'Type 3', 'group-types' ) ?></label>



<div id="group-details">

<p><?php _e( 'We will automatically create a group for your business or organization. This group will be tailored to your needs! You can change the description and the news later in the admin section of your group.', 'group-types' ); ?></p>



<?php do_action( 'bp_group_name_errors' ) ?>

<label for="group_name"><?php _e( 'Group Name', 'scuba' ) ?> <?php _e( '(required)', 'buddypress' ) ?></label>

<input type="text" name="group_name" id="group_name" value="" />

<br /><small><?php _e( 'We suggest you use the name of your business or organization', 'group-types' ) ?></small>



<label for="group_desc"><?php _e( 'Group Description', 'scuba' ) ?></label>

<textarea rows="5" cols="40" name="group_desc" id="group_desc"></textarea>

<br /><small><?php _e( 'This description will be visible on your group profile, so it could be used to present your mission statement for example.', 'group-types' ) ?></small>



<label for="group_news"><?php _e( 'Group News', 'scuba' ) ?></label>

<textarea rows="5" cols="40" name="group_news" id="group_news"></textarea>

<br /><small><?php _e( 'Enter any news that you want potential members to see.', 'group-types' ) ?></small>

</div>

</div>

<?php

}

add_action( 'bp_before_registration_submit_buttons', 'sv_add_registration_group_types' );

Then we have to validate things and add some usermeta when a regitration happens:

/**

* Add custom userdata from register.php

* @since 1.0

*/

function sv_add_to_signup( $usermeta )

{

$usermeta['account_type'] = $_POST['account_type'];



if( isset( $_POST['group_name'] ) )

$usermeta['group_name'] = $_POST['group_name'];



if( isset( $_POST['group_desc'] ) )

$usermeta['group_desc'] = $_POST['group_desc'];



if( isset( $_POST['group_news'] ) )

$usermeta['group_news'] = $_POST['group_news'];



return $usermeta;

}

add_filter( 'bp_signup_usermeta', 'sv_add_to_signup' );



/**

* Update usermeta with custom registration data

* @since 1.0

*/

function sv_user_activate_fields( $user )

{

update_usermeta( $user['user_id'], 'account_type', $user['meta']['account_type'] );



if( isset( $user['meta']['group_name'] ) )

update_usermeta( $user['user_id'], 'group_name', $user['meta']['group_name'] );



if( isset( $user['meta']['group_desc'] ) )

update_usermeta( $user['user_id'], 'group_desc', $user['meta']['group_desc'] );



if( isset( $user['meta']['group_news'] ) )

update_usermeta( $user['user_id'], 'group_news', $user['meta']['group_news'] );



return $user;

}

add_filter( 'bp_core_activate_account', 'sv_user_activate_fields' );



/**

* Perform checks for custom registration data

* @since 1.0

*/

function sv_check_additional_signup()

{

global $bp;



if( empty( $_POST['account_type'] ) )

$bp->signup->errors['account_type'] = __( 'You need to choose your account type', 'group-types' );



if( empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )

$bp->signup->errors['group_name'] = __( 'You need to pick a group name', 'group-types' );



if( ! empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )

{

$slug = sanitize_title_with_dashes( $_POST['group_name'] );

$exist = groups_check_group_exists( $slug );

if( $exist )

$bp->signup->errors['group_name'] = __( 'This name is not available. If you feel this is a mistake, please <a href="/contact">contact us</a>.', 'group-types' );

}

}

add_action( 'bp_signup_validate', 'sv_check_additional_signup' );

And then we set up the group for the user (there are some constants in this function, so you’ll need to change that):

/**

* Create custom groups for skools, biz and org accounts

* @since 1.0

*/

function sv_init_special_groups( $user )

{

global $bp;



// get account type

$type = get_usermeta( $user['user_id'], 'account_type' );



if( $type == 'normal_user' )

{

// Do nothing

}

elseif( $type == 'type_one' || $type == 'type_two' || $type == 'type_three' )

{

// get some more data from sign up

$group_name = get_usermeta( $user['user_id'], 'group_name' );

$group_desc = get_usermeta( $user['user_id'], 'group_desc' );

$group_news = get_usermeta( $user['user_id'], 'group_news' );



$slug = sanitize_title_with_dashes( $group_name );



// create dive skool group

$group_id = groups_create_group( array(

'creator_id'	=> $user['user_id'],

'name'			=> $group_name,

'slug'			=> $slug,

'description'	=> $group_desc,

'news'			=> $group_news,

'status'		=> 'public',

'enable_wire'	=> true,

'enable_forum'	=> true,

'date_created'	=> gmdate('Y-m-d H:i:s')

)

);

// add the type to our group

groups_update_groupmeta( $group_id, 'group_type', $type );



// delete now useless data

delete_usermeta( $user['user_id'], 'group_name' );

delete_usermeta( $user['user_id'], 'group_desc' );

delete_usermeta( $user['user_id'], 'group_news' );



// include PHPMailer

require_once( SV_MAILER . 'class.phpmailer.php' );



$mail = new PHPMailer();

$mail->IsSMTP();

$mail->Host = SV_SMTP;



$auth = get_userdata( $user['user_id'] );

$profile_link = $bp->root_domain . '/' . $bp->groups->slug . '/' . $slug . '/admin';



$message = sprintf( __( 'Hello %s,



we have created a group for your business or organization. To get more out of your presence on Yoursitenamehere please take some time to set it up properly.



Please follow this link to fill in the rest of your profile: %s



We wish you all the best. Should you have any questions regarding your new group, please contact us at support@yoursitenamehere.com.



Your Yoursitenamehere Team', 'group-types' ), $auth->display_name, $profile_link );



$mail->SetFrom("support@yoursitenamehere.com","Yoursitenamehere");

$mail->AddAddress( $auth->user_email );



$mail->Subject  = __( 'Your new group pages on Yoursitenamehere', 'group-types' );

$mail->Body = $message;

$mail->WordWrap = 75;

$mail->Send();

}

}

add_action( 'bp_core_account_activated', 'sv_init_special_groups' );

When you write a group extension we’ll have to swap the activation call with a function like the one below to be able to check for group types.

/**

* Replacement activation function for group extension classes

*/

function activate_type_one()

{

global $bp;

$type = groups_get_groupmeta( $bp->groups->current_group->id, 'group_type' );

if( $type == 'type_one' )

{

$extension = new Group_Type_One;

add_action( "wp", array( &$extension, "_register" ), 2 );

}

}

add_action( 'plugins_loaded', 'activate_type_one' );

The last thing we need to do is add our group type names to group and directory pages:

/**

* Modify the group type status

*/

function sv_get_group_type( $type, $group = false )

{

global $groups_template;



if( ! $group )

$group =& $groups_template->group;



$gtype = groups_get_groupmeta( $group->id, 'group_type' );

if( $gtype == 'type_one' )

$name = __( 'Type 1', 'group-types' );



elseif( $gtype == 'type_two' )

$name = __( 'Type 2', 'group-types' );



elseif( $gtype == 'type_three' )

$name = __( 'Type 3', 'group-types' );



else

$name = __( 'User Group', 'group-types' );



if( 'public' == $group->status )

{

$type = sprintf( __( "%s (public)", "group-types" ), $name );

}

elseif( 'hidden' == $group->status )

{

$type = sprintf( __( "%s (hidden)", "group-types" ), $name );

}

elseif( 'private' == $group->status )

{

$type = sprintf( __( "%s (private)", "group-types" ), $name );

}

else

{

$type = ucwords( $group->status ) . ' ' . __( 'Group', 'buddypress' );

}



return $type;

}

add_filter( 'bp_get_group_type', 'sv_get_group_type' );



/**

* Modify the group type status on directory pages

*/

function sv_get_the_site_group_type()

{

global $site_groups_template;



return sv_get_group_type( '', $site_groups_template->group );

}

add_filter( 'bp_get_the_site_group_type', 'sv_get_the_site_group_type' );

It’s quite a bit of code, but it should get you started. This hasn’t been tested with 1.2 btw.

The ideal solution for me is a preference/settings pane where you can assign ‘other’ profiles to your own.

Say I create an account on testbp.org with the username ‘testing’, and then visit ‘testbp.org/members/testing/settings/connect’ I could then select which other accounts I wish to attach to this main account: Facebook, Twitter, Google etc. by simply pressing a button.

I’m not sure how this could work, but it would negate duplicate accounts, and would allow me to be signed in when I already am in FB or Twitter etc.

There are just so many different accounts we can integrate with, it would be a shame for site owners to have to choose just one…

Found the solution for my problem (described above). I had the setting “Allow new registrations” set to “Only logged in users can create new blogs.”, which actually caused the 302 redirect. I changed the setting to “Only user account can be created.”, which in my case is the correct setup.

What are we talking about here guys? Only the blog creators will ever see the dashboard on a regular basis. All the users that are subscribers will rarely if ever see it. Create a subscriber account for yourself and check that for yourself. I think you all are being too demanding on software that is so young. BuddyPress as an add on to a blogging/CMS platform is what I want, not the other way around. If we go that route what are going to end up with? Gifts?

I think you all might want to check out some of those other software suites I mentioned previously (out of that bunch I really like Social Engine).

BTW the thought of gifts makes me vomit just a little…

Hi Marius – I have a question. I just uploaded a fresh copy of Groupblog, deactivated the plug-in, reactivated it and then went to check it on the site. I’m seeing the groupblog content inserted on the group home page – I had created two posts prior to the upgrade which are still visible, but when I click the “blog” link in the menu, I get a page not found error.

I thought maybe I had to move the page templates into my theme but that didn’t change anything.

If you want to take a look, you can hit the group directly with this link.

http://holisticground.com/groups/animation-order/home/

It’s the “Blog” link in the tabbed menu at the top of the content area that’s causing me the trouble, even tho clearly the plug-in is inserting the groupblog data in the areas below it.

PLEASE NOTE: That site is full of dummy data to make development easier. If necessary, you can create an account if it helps. I have that enabled.

Ok. I’ve fixed it.

The mailer checks the domain name used. I won’t exted on this issue.

To let our local mailserver work correctly, we can do it by changing the validate_user_signup() function.

This function is located in: /wp-signup.php file, check it at the line 267 or something similar.

We must tell wordpress to consider valid our mail domain name without restrictions.

This can be done by modifying the user account check line:

We must replace the sentence

if ( $errors->get_error_code() )

by

if ( $errors->get_error_code() && $_SERVER[‘HTTP_HOST’]!“localhost.YOURDOMAINNAME” ).

Doing this, WP will accept any mail and user name if sent from our local domain.

Notice that WP won’t warn us about any registration error by doing this.

If you create by mistake an account, you can erase this sign up by editing the signup table in your wprss database using phpmyadmin.

I hope it can help anyone else.

‘wp_bp_activity_sitewide’ doesn’t exist anymore, not even in the deprecated code. It was dropped pre 1.0 in lieu of having one universal activity stream. A clean 1.1.3 installation shouldn’t have any code looking for those tables.

http://socialpress.co.za/activity/feed works for me.

I’ve created a test account on your website and confirmed that I was able to delete my own activity just fine.

Is it possible this is a conflict with the privacy component?