BuddyPress.org

Do you use a custom function building a widget ?
if you used the old php4 method
parent::WP_Widget( false, $name = __( 'My widget' ) );

you should now use
parent::__construct( false, $name = __( 'My widget' ) );

This can also be in a theme or a plugin. BuddyPress use _construct method and is not concerned.

If you deactivate WP_DEBUG in wp-config, the notice will disapear. And it’s only a notice, nothing will sudenly stop to work.

Deprecating PHP4 style constructors in WordPress 4.3

Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use __construct()

BuddyPress roadmap:
https://buddypress.trac.wordpress.org/milestone/2.3.3

@chevalhack, of course it is ! This forum is installed on WP 4.3. What is not working… do you see warnings or notice ? Give details please !

@toggerybob, seems it’s your membership plugin who brings these warnings.
If it is Memberhip 2, it was updated today.
https://wordpress.org/plugins/membership/

BuddyPress use bbPress when you allow group forums.
If the group is private, the attached forum is also hidden ton non members of that group. Same for public or private groups.

You don’t have to change the group forum setting in the forum list.
The right steps
Create a group A
A is set to private
Allow a forum for A
—— The wrong step ——–
Going to dashboard forum admin, and set forum A to private. If you do this nobody will see it except site admin.

Groups

https://buddypress.org/support/topic/hide-buddypress-and-bbpress-items-from-guests/
https://buddypress.org/support/topic/buddypress-private-group-is-not-visible-in-bbpress/

Please d’ont double post.
https://buddypress.org/support/topic/buddypress-forum-hidden-group-but-still-visible-on-page-by-members/

Readers, see also this plugin used to hide XProfile Field groups from different user types based on the user’s role.
https://github.com/tannerm/buddypress-conditional-field-groups

@ricsca2 – you are wise to be weary of plugins that are not in the wp-repo – but I think for the wrong reason. I am more concerned that plugins have not had the extra security checks that are run through the official repo. However I have seen more useful plugins for BP outside of the official repo – like the updated one for affecting the activity stream blocking – only on github, ones that get good support on wpmudev, etc.

I want to have faith in the ‘media press’ mentioned above, and I bet many are using it successfully – so it’s worth a try for a short term solution.

You concern about “extensions unofficial because if the developer ceases to update them” – should go beyond things in or not in the wp dot org repo – and it is a valid concern given the history of WP / BP and plugins in general – especially in regard to photo uploads / handling.

Back in the day it was “bp-album” – in the repo – worked. Support ceased – abandoned. Updates to wp / bp broke it.

Rtmedia came in (and for a very short while there was actually an importer / exported from bp-album to rtmedia!) – things have changed – rtmedia is likely the most used plugin for BP – and now they have made it an over-bloated POS (IMHO) – and now when things break they only offer support for paid / premium addons.

(begging for media export options here: https://buddypress.org/support/topic/rtmedia-export-script-attachments-api/

Now there are some other options – still no way to export the data. There are some things being worked on – but nothing definitive. Some great foundations being laid (bpattachments now a (not yet used) thing) –

This is why I have asked time and time again for picture / media handling to be added to BP core –
most recently a year and half ago (https://buddypress.org/support/topic/photos-albums-media-please/ ) – plus in the buddypress surveys.
so future updates will consider breaking this very important piece of live social networks.

However for now we are stuck with not knowing if things are going to work now, or next update. Just like we have been for years..

You’re declaring 3 arguments, but only one is given if you are testing this localy.
Possible local scenarion you used:
– you create a new user
– you login as admin and activate the pending user. You get 3 warnings. Logout.
– login as new user.
– you see the message

Remove $key & $user and redo the same and all went fine.
Use function send_msg_to_new_member( $user_id ) and change 3 to 1.
Add also a conditional check to test if the messages component is active. (see link blow).

Not tested yet on live site.

This was originally published by @henrywright here:
https://buddypress.org/support/topic/deliver-custom-message-via-buddypress-to-new-users/#post-229688

BP’s registration template is in: https://buddypress.trac.wordpress.org/browser/tags/2.3.2/src/bp-templates/bp-legacy/buddypress/members/register.php

Copy it to your child-theme, /your-theme/buddypress/members/register.php, and make your change in that copy.

In some case, you could also use bp_get_template_part filter.

@dineshravajani07, searching this forum for “login widget” have brought many answers.

Styling BuddyPress Login Widget

https://buddypress.org/support/topic/how-to-addinsert-buddypress-registration-form-in-a-pagehomepage/

Hi @david-ar,

if you expect for help, give detais related to BuddyPress, not FB. Which option are you talking about?
https://buddypress.org/support/topic/when-asking-for-support-2/

Yes, I think you can. Try this:

function my_username_validation() {
    if ( strlen( $_POST['signup_username'] ) > 16 ) {
        global $bp;
        $bp->signup->errors['signup_username'] = __( 'Put your error message here.', 'buddypress' );
    }
}
add_action( 'bp_signup_validate', 'my_username_validation' );

if the developer ceases to update them This problem is the same for official or unofficial plugins.

Brajesh is a long year and well knowed buddypress plugin developper, you can trust his awesome work !
https://profiles.wordpress.org/sbrajesh#content-plugins

I am writing all these code in bp-functions.php in my bududdypress folder within my theme folder. (this may be my problem).

Yeah, it is probably the problem. Custom functions for BP can/should be added to bp-custom.php, which should sit in wp-content/plugins/bp-custom.php, not in your child theme buddypress folder.

Or into functions.php of your child-theme.

bp-custom.php explained on Codex.

Here an example for profile field lenght with some comments.

function bpfr_custom_textfield_length() {	
	
	//Check if user is logged in & if xprofile component is activated
	if ( is_user_logged_in() && bp_is_active( 'xprofile' ) ) :	
	$my_custom_textfield = bp_get_member_profile_data( 'field=Brief Biography&user_id='.bp_get_member_user_id() );	
	
	/* 
	 * The length = number of characters, not words.
	 * Set the number of caracters to show. 
	 * The 3 dots are the appended text ending the excerpt.
	 * Don't remove the quotes if you change this
	 * BuddyPress 2.1 will add new class and id for custom fields. 
	 * The span can be omited to style this part. See ticket #5741
	 */
	if ( strlen($my_custom_textfield) > 20) :  //adjust to your need
	$my_custom_textfield = substr($my_custom_textfield, 20).'...'; //adjust to your need
	endif;
	// uncomment the following line to get a span around the displayed field content
	// echo '<span class="short-custom">'. $my_custom_textfield; .'</span>';
	// comment the following line if you use the span
	echo $my_custom_textfield;	
	
	endif; // is_user_logged_in
}
add_action( 'bp_directory_members_item', 'bpfr_custom_textfield_length' );

Ticket #5741

Hi @ramuzic,

read the related ticket for more explanation from here:
https://buddypress.org/support/topic/warning-strstr-empty-needle/#post-239979

If the error is still in after changing to one of twenty theme, it’s possible you use a cache plugin containing some old files or your browser history is…very old. Clear it !

Have you tried the BuddyPress Limit Friendship plugin?

@danbp I needed your answer 1 year 6 months ago 🙂

per_page option is availble for the message loop, like inbox (which is default), sentbox and notices where all received message are stored. This option let you paginat the result.

Now, the case of a long conversation. This start in the inbox, where you found it at page 1 or 12…
You click on the message and you see the content. This page is not concerned by the loop containing your per_page option. You can control that in the url.

If you read the code in the file i indicated you previously, you’ll see that there is no pagination system in it.

Message option can be set in bp-templates\bp-legacy\buddypress\members\single\messages\message-loop.php

You need to copy this file into your child-theme first so you won’t loose your modification at next update. See codex if you need more infos about theming.

@ch1n3s3b0y,

A username is not a real name and wordpress use only username, email and password (the only real security point) to allow access.
And the default behavior of WordPress is to set the nicename equal to the username. So, where is the security issue ?

If you’re affraid by the Name field coming with BuddyPress during registration, rename it to Pseudonyme and you’re done. The field must contain a value, which can be first name, last name or whatever. The value is mandatory, not the name as name… ch1n3s3b0y is certainly not your name !

You’re asking to replace the username by a another value collected with the same register form. Do you think that such other field has less importance in regard of security ? Why would the username be critical and the custom field not ?

You can even disallow dashboard access to your subscriber, so they never can change anything outside of what is on hand on front-end profile management.

Please read here to calm you down (hopefully) 🙂

Why Showing The WordPress Username Is Not A Security Risk

You can try this plugin by BuddyDev

BuddyPress Non Editable Profile Fields