BuddyPress.org

https://codex.wordpress.org/WordPress_Menu_User_Guide
As part of a wordpress plugin, BP menu use the same technique.

hi @gatera,

It’s only a PHP notice, and harmless in regard of a PHP Warning message. Apparently, your plugin is not completely compatible with BuddyPress or at least called to early or something like that.

You must debug your install.
https://codex.wordpress.org/Debugging_in_WordPress

More about bp_setup_current_user function
https://buddypress.org/support/topic/debug-error-bp_setup_current_user-was-called-incorrectly/?view=all#post-186116
https://buddypress.trac.wordpress.org/ticket/4830

File ref: buddypress/bp-core/bp-core-dependency.php
Documented function: http://oik-plugins.eu/buddypress-a2z/oik_api/bp_setup_current_user/

Thanks @gatera! It might just be reflecting a problem in the other plugin, but I’ve created a bug report for BuddyPress and we’ll look into it sometime to see if it’s our fault or if there’s something we could be doing better. Thanks for letting us know:

https://buddypress.trac.wordpress.org/ticket/5957#ticket

After lots of searching I finally got round the problem of BP/WP not taking you to the registration page by adding the following file into wp-content/plugins/

bp-custom.php

<?php
/**
* Disables BuddyPress’ registration process and fallsback to WordPress’ one.
*/
function my_disable_bp_registration() {
remove_action( ‘bp_init’, ‘bp_core_wpsignup_redirect’ );
remove_action( ‘bp_screens’, ‘bp_core_screen_signup’ );
}
add_action( ‘bp_loaded’, ‘my_disable_bp_registration’ );

add_filter( ‘bp_get_signup_page’, “firmasite_redirect_bp_signup_page”);
function firmasite_redirect_bp_signup_page($page ){
return bp_get_root_domain() . ‘/wp-signup.php’;
}

This dispenses with BP’s registration system and falls back to the standard WP registration.

What is redirecting ? BP Redirect to Profile is not updated since over a year and many things have changed since (given to be compatible to 1.7….)
Also it was intended for:

• Redirect all normal users to their profile on login
• If the admin logs in from site front page,redirect him back to front page.
• If the Site Admin logs in from site backend, i.e. using http://yoursite.com/wp-login.php, let him go to the WordPress dashboard

You didn’t answered: what is the login plugin ?

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

I wrote:
If the question is How to style the HTML of the messages (ok with a french accent, but seriously, is it so ambiguous? 🙄 ) On each WordPress plugin page, you have a description. Read it !

Of course it’s possible and explained on this Codex page:
https://codex.wordpress.org/Widgetizing_Themes

But before, check your theme support. Maybe there is something related to mobile device ?

@tac28
A child theme is something you create that can inherit styles, functions, layout, etc. from the parent theme you use. You have to be using some sort of theme now so you would make a child theme that inherits from a parent theme and you can make your customizations in the child theme. This way your customizations are not overwritten when you update the parent theme. Please review:
https://codex.wordpress.org/Child_Themes

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. 😉

Why do you want to use code to add a widget to a theme ?

Go to dashboard > Apparence > Widget and do your stuff from there.

If your theme has widgetized areas, this is how you have to do. BP is only a plugin, not a “site” or a CMS.

Of course, if you build your own theme from scratch, you have to create such areas first in the theme’s functions.php.

https://codex.wordpress.org/WordPress_Widgets
https://codex.wordpress.org/Widgetizing_Themes

@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.

@el_ganadores

There’s a trac ticket about this….

https://buddypress.trac.wordpress.org/ticket/5931

It’s probably because you’re using WP New User Approve which may not work with BuddyPress. See author comment and check the recent update changelog. BP problem seems not be solved yet.
Deactivate the plugin and give a try.

Or consider perhaps this plugin.

hi @ahd904,

behind your tech question, two things need some clarification at least.

First:

I just want to hide some of the group creation steps as these might make the users think too complicated to join the community.

Register process doesn’t include group creation, nore joigning a group, so i guess you are thinking about a problem that doesn’t exist at this stage.

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. Anyway in this case, simply deactivate group creation for users and create users groups yourself.
Assuming that you don’t think it’s too complicated for the user to click on “join group” ! 🙄

As @bphelp said with reason, what your question implies needs some extra coding and much more as a simple snippet. You can do many things with BuddyPress, but not everithing or anything. 😉

Second:
Core simplification is a hard work (see Trac), so don’t expect that your goal could be reached easily, as BP will never be a “one click” tool. IMO this plugin is already very easy to use as is.

That said, you could imagine your project differently and perhaps apply another strategy.
For example, the ability for users to join automatically a group at registration. 2 plugins can do that actually.

• This one allows a new BuddyPress user to select groups to join during the registration process. You create the group, user choose his group.
• This one create a new Group when a new user sign up. But what will happen when you have 50 registration by day, spammers included ?

In both case, pros and cons have to be considered.

if you love the snippets and sweat on your site, here are two other options.

• Snippet: automatically add new user to a group
• Snippet: allow new user to be auto joined to groups you select from the admin (from core dev @imath). Explanation in french, coded in english – of course ! 🙂 )

To create a member only site, I would highly recommend this plugin – https://wordpress.org/plugins/jonradio-private-site/

There are some plugins that export data.
google: buddypress export members

For example, for site admins:
https://wordpress.org/plugins/export-user-data/

For front-end, you could extend that plugin or find something else.

hi @flickchicks,

take example from the TOS at the bottom of this page. But you probably have to inquire for something more accurate with the dutch law, depending your project.

https://buddypress.org/support/topic/accept-site-terms-and-conditions/
http://wordpress.stackexchange.com/questions/81935/add-first-name-last-name-date-of-birth-and-terms-and-conditions-to-reg

it is not intended by default. bbPress use a simplified version of tinyMCE and image upload are not included, for security reasons. Allowing forum users to access the media library of all your site is probably not what you want…

To the above mentionned plugins, there are also BuddyDrive and MediaPress, a new plugin who permit any user to upload media files (photo, audio,video,doc) to his profile page, that way it is very simple for each subscriber to share his stuff, even on the forum, by just giving a link to his media gallery.