BuddyPress.org

I’m not aware of a plugin that can do exactly that? Perhaps some of the guys on here know of one?

To do it manually, you could hook a function to init and work from there. For example:

function my_function() {

    if ( ! is_user_logged_in() && bp_is_current_component( 'messages' ) ) {
        // Current user is not logged in so don't let them see stuff. In this case, private messages 
        wp_redirect( home_url() );
        exit;
    }
        
    $flag = false;
    // Get current user info.
    $user = wp_get_current_user();

    if ( ! in_array( 'student', $user->roles ) ) {
        // The current member is not a student.
        $flag = true;
    }

    if ( $flag && bp_is_current_component( 'messages' )  ) {
        The currently logged-in member is not a student and is trying to view private messaging. Let's redirect them away.
        wp_redirect( home_url() );
        exit;
    }
}
add_action( 'init', 'my_function' );

From that, you should be able to see how you can achieve what you’re trying to do without the need of a plugin.

Refs:

Template Tag Reference

https://codex.wordpress.org/Function_Reference/wp_redirect

Note to lazy people

Definetly using the orange search button on the top right corner of this forum mostly brings good advice. But YOU have to search a bit before asking ! 😀

https://buddypress.org/support/topic/making-buddypress-private/

More ?
https://buddypress.org/support/search/private/

Don’t know your code !
The BuddyPress login widget code looks like this: (source:/buddypress/bp-core/bp-core-widgets.php)

<form name="bp-login-form" id="bp-login-widget-form" class="standard-form" action="<?php echo esc_url( site_url( 'wp-login.php', 'login_post' ) ); ?>" method="post">
	<label for="bp-login-widget-user-login"><?php _e( 'Username', 'buddypress' ); ?></label>
	<input type="text" name="log" id="bp-login-widget-user-login" class="input" value="" />

	<label for="bp-login-widget-user-pass"><?php _e( 'Password', 'buddypress' ); ?></label>
	<input type="password" name="pwd" id="bp-login-widget-user-pass" class="input" value=""  />

	<div class="forgetmenot"><label><input name="rememberme" type="checkbox" id="bp-login-widget-rememberme" value="forever" /> <?php _e( 'Remember Me', 'buddypress' ); ?></label></div>

	<input type="submit" name="wp-submit" id="bp-login-widget-submit" value="<?php esc_attr_e( 'Log In', 'buddypress' ); ?>" />

	<?php if ( bp_get_signup_allowed() ) : ?>

	<span class="bp-login-widget-register-link"><?php printf( __( '<a href="%s" title="Register for a new account">Register</a>', 'buddypress' ), bp_get_signup_page() ); ?></span>

	<?php endif; ?>
</form>

You hardcoded several things.
<label for="bp-login-widget-user-login">שם משתמש</label>
and
<input type="text" name="log" id="bp-login-widget-user-login" value="" width="10" />

Be warned that such hacks will be overwriten at next BuddyPress or theme update.
Modifications should only be done in a child theme.

Begin to remove width=”10″ to fit to the original code. And see if this change something. If not, try

input#bp-login-widget-user-login {
   width: 100%!important;
}

hi @funkolector,

It’s only a message, not a bug, who depends of the browser you use, your debug tool severity…. and the load order of some js files (from theme or plugins). And TypeError on BP Trac are rare.

It’s anyway very variable, et puis quoi, is your site crashing or is something NOT working AT ALL once you created such a field type ?

I’m asking because i have such js error message over years with my BP sites… and never had any dramatically issues with js. Maybe weird, but only if you check constantly the debug console. 😉

The original register.php file is in bp-templates/bp-legacy/buddypress/members/register.php

You copy this file and add it to your child-theme (mandatory in such case), to get:

/your-child/buddypress/members/register.php

It is in this copy where you do your modification.

Remenber also to never modify a core file directly, as you will loose your work at the next update.

References: https://codex.buddypress.org/themes/

hi @ideasdesigninc,

can this be done by editing a language file ?

Yes, this is also best practice and the easiest way to do that, even if your site is in english.

Customizing Labels, Messages, and URLs

And here a somehow recent tutorial about filtering such messages.

Also to be clear, when it’s time to use, we all made errors. So “it’s not working” is mostly because we did something wrong. 😉

This is a cosmetic question which can be solved by CSS from within your child-theme.

https://buddypress.org/support/topic/change-textbox-size/

Members are the heart of BuddyPress. When a user register on a BP activated site, this user is automatically a “member”.

So i guess “they are not registering for the site, just the members area” is just impossible. Don’t know what you already did to get a “private” member area, but if you have an issue, it’s mostly because you did something wrong. 😉

To confirm to readers what you already get to work:

To modify the registration page, on which appears the login fields belonging to WP (user, username, email & password), BP adds his own additionnal fields, under condition you activated the xProfile component.

By default, BP add only one field in the mandatory field group “Base”: NAME.

When the admin add a new field, he can choose between different field status, and depending this status, you will see phrase such as “This field can be seen by: “.

These settings are avaible in Dashboard > Users > Profile Fields

@tsabar,

the widget remain in english because the translation is missing.

The hebrew version on GlotPress, where BP picks the automatic translation in your language is not completly translated (64%).

Download it and finish the translation on your computer. BP comes with a buddypress.pot file which you must use to do this. And use poEdit or a similar software.

Concerning the widget, you have to translate this string in the po file:
<a href=\"%s\" title=\"Register for a new account\">Register</a>

Aside, bp and po files are always in UTF8.
If you save a po file in ANSI, you have to use exclusively ANSI without BOM (.txt format and evtl. change the file extension to your need)

To generate the mo file, you must use a compiler like poEdit.

Also avoid to hack core files and don’t make a translation on the admin side.

I’ll find more details around how to translate in some previous topics, since 2.1 is out.

If you have an activity like User A rated Movie A with 9/10, means that you use a rating plugin or similar system. This isn’t part of BuddyPress.

You have probably better to ask this plugin author for an improvement or a new feature.

Might this even be something to add to the core?
Don’t think that such a big count of grouped activities would be appreciated, as such an improvement could dramatically slowdown a site.

hi @tac28,

as you’re a first timer, i would suggest that you read attentively the Codex, and try to understand how BuddyPres works.

I am using a child theme based on Headway Base and have no need of a bp theme.

You can use any theme you want with BuddyPress.

Modifying the registration page is explained here.

xProfile fields settings is explained here.

If you allow your users to create groups, they have to follow the 3 creation steps, because it is intended so in BuddyPress. Thinking that this might be to complicated, implies that you think that your users are not able to do this. Mabe you’re right, but maybe not.

About this i have worked with other plugins to tell more about groups, media ability and add location etc. So i now have 7 steps in a group creation. This is the main reason why i am requesting for this topic.

This doesn’t really make any sense how can you think you need to limit creation steps if you add plugins that extent the group creation api in offering necessary user choices in the setup process, are they not presented as ‘steps’ because they are choices a user needs to select.
However if you would simply prefer that a default choice is initially set and setup screen for that option hidden then it sounds like you need to modify those plugins behaviour which may mean hacking filtering into the plugin or contacting the author for a modification to remove that setup tab – but preserving edit screens if available.

@focallocal
If your permalinks haven’t been changed since installing BuddyPress you should see a reminder in the dashboard near the top of the dashboards page that displays the notice that the permalinks need to be changed to something other than default for BuddyPress to work properly.

@focallocal, please don’t double post.
Answered here: https://buddypress.org/support/topic/register-broken-page-refreshes-seen-problem-posted-often-but-no-solutions/

Hi @kgumhiok,

you say nothing about what you want to do ! And you use a premium plugin which is not part of BuddyPress. Sorry but i’m afraid we can’t help you. Ask eigther on plugin support.