BuddyPress.org

Try switching to a WP theme like 2015 to see if the issue really is BP and not your theme.
You can file a bug report here:
https://buddypress.trac.wordpress.org/

Hiya,

There seems to be a compatibility issue with the current version of Buddypress and the latest WordPress 4.8 update. I noticed that all the elements available for users on Buddypress suddenly disappeared as soon as I made the WordPress update. I checked it against one of my other websites which I have not updated yet to WordPress 4.8 and installed Buddypress there and all the elements are visible.

Is there anything I could do in the meantime to fix the problem whilst I wait for the latest BuddyPress update as the website in question is due for launch today, but unfortunately i made the WordPress update late last night which affected the elements I need for the site to function as intended with the use of BuddyPress as an aid.
Thank you in advance

E.

BuddyPress 2.8.x works OK with WordPress 4.8.

BuddyPress 2.9 is due out in the next few weeks.

This is fixed in the development branch of 2.8.

In the meantime, you can manually apply the following fix until 2.8.3 is released:
https://buddypress.trac.wordpress.org/changeset/11520

Hi @babcoltd

You will need to sync the value of your xProfile field with a WordPress role to get this working. I’m not sure that a plugin is available so as far as I know it will need to be custom developed.

You may use my Redirect to profile plugin.
It does exact same thing.

BuddyPress Redirect to Profile

Hope that helps.

Have you tried: https://wordpress.org/plugins/bp-simple-private/ ?

You can also get it from PhiloPress.

Hi @giuseppecuttone

The BuddyPress Trac ticketing system is the way to follow BuddyPress development. You can view open tickets and even contribute patches and bug reports.

This is a bbPress bug, which is scheduled to be fixed in bbPress v2.6.

See https://bbpress.trac.wordpress.org/ticket/2690.

In the meantime, manually add the following fix:
https://bbpress.trac.wordpress.org/changeset/5857

For busy sites, removing old entries can increase performance.

Have you tried BP Bulk Delete ?

You can also get it at PhiloPress.

Read this conversation in its entirety.

The plugin author was kind enough to guide me through the process of making that work. If you follow those instructions, your users will be able to upload their profile photo during registration.

Although this method works, it causes a slight problem: The users won’t be able to update their photo in the future, because the default Buddypress “Change avatar” function refers to a different file, or location, than the xprofile custom fields type location.

If you find a way to fix that problem, please let me know.

There is a plugin called BP Simple Private that allows you to restrict access to all Buddypress pages to logged in users only. Then, if people try to visit Buddypress pages after you install the plugin, they will get redirected to the home page.

But if I’m understanding you wrong – and you want to have a separate site just for your buddypress groups, then I will recommend setting up WordPress Multisite.

And if I’m understanding you right – which bells and whistles do you want to disable? I’ve disabled a few things with CSS & PHP hacks – but like what do you want to see gone?

Designing endpoints is perhaps the major issue for this API and the subject of much discussion.

I would encourage you to use the Issues tab on the repo:
https://github.com/buddypress/BP-REST

There is also a BuddyPress Slack channel. From the repo readme:
Weekly BP REST API dev chat are held on Wednesdays at 22:00 UTC in WordPress Slack channel #buddypress

I think I finally understand what is going wrong here. If you pass a bad group object to bp_group_has_moderators() or don’t pass a group object and the global $groups_template->group isn’t set, this error can occur.

If you’ve had this problem, can you please respond telling me what theme you’re using? Furthermore, look in your theme where bp_group_has_moderators() is called, and tell me if it’s being called with a $group argument (like bp_group_has_moderators( $group_object ) ) or without an argument (like bp_group_has_moderators() ).

Do you also see an entry in your error log like the following or not?
Trying to get property of non-object in /Users/dcavins/Sites/develop.git.wordpress.org/src/wp-content/plugins/buddypress/src/bp-groups/bp-groups-template.php on line 2576

Thanks for your help,

-David

@vanessenstudio Given the screenshot, I can only guess that your theme’s stylesheet is missing lines 601 through 614 which are necessary to move the notice to the top of the page.

Try this : https://bpdevel.wordpress.com/2016/08/05/nouveau-a-bp-template-pack-story/
I am also building a plugin for this, which would be available within few days.

BuddyPress themes are basically WordPress themes. Technically all themes “should” be compatible with BuddyPress.
If you’re looking more into template overriding then check the documentation link above.

Try this : https://themeforest.net/item/kleo-pro-community-focused-multipurpose-buddypress-theme/6776630, https://themeforest.net/item/wplms-learning-management-system/6780226 , https://themeforest.net/category/wordpress/buddypress

Regarding your question :
Check existing topics in this forums, this has been answered several times.

Add tab to user profile from plugin

Have you tried: BP Simple Private ?

Without code it might be a bit more work but definitely doable.

If you want most of your site blocked off for non members you could use a plugin like BuddyPress members only

For specific blocking of pages, I would use the buddypress settings in combination with Advanced Access Manager
the latter will allow you to be very narrow with you access permission.

Good luck 🙂

Extended Buddypress profile fields demands an additional name / username field. This is the case whether you are using Buddypress Usernames Only plugin or not.

This is only relevant if you require extended profile fields. If you don’t, then go into Buddypress settings and turn off extended profiles. That will remove the requirement for a second name on the registration / profile area.

If you want to use extended profile fields on BP, but you don’t want the second username / name field uglying up your registration flow, you can do the following.

You have to be careful with this, because if you hack it, remove the second required name / username field, or any of a dozen other solutions I’ve found – the registration will break down. You will get 500 errors, missing confirmation emails etc.

The solution I used for this is as follows.

1. Assuming you just want to use a singular Username for your site – install the Buddypress Usernames Only plugin. It says the plugin is old but it is still working as of WP version 4.7.4 (for me at least). This deals with the display / access of various username / name / fullname / nickname issues throughout the WP / Buddypress install.

2. Next you’ll need to hide the extra name / username field on the registration area, and the BP profile area. Stick this CSS into your theme custom CSS under Appearance > Customize:

#profile-edit-form .field_1 { display: none;}
#signup_form .field_1 { display: none;}

(I have seen a 3rd line of CSS on other solutions – #register-page p { display: none;} – all this did for me was to hide the confirmation message after the user registers. You probably want that so I’d leave that line out).

3. The fields should now be hidden, but the system still requires that information to process properly. So next create a file in notepad and save it as name_remove.js

In that file put the following javascript:

document.getElementById("signup_username").onchange = function() {myFunction()};
function myFunction() {
 var x = document.getElementById("signup_username");
document.getElementById("field_1") .value = x.value
}

Save that file and upload it to your theme folder (same folder as functions.php etc). This javascript automatically populates the hidden field with the username, so the system does not complain or fall over.

4. Finally you need WordPress to pick this javascript file up. You can do that with a function, using file enqueing. Copy and paste this function into your themes functions.php file Appearance > Editor

function wpb_adding_scripts() {
wp_register_script('name_field_remove', get_stylesheet_directory_uri() . '/name_remove.js', array('jquery'),'1.1', true);
wp_enqueue_script('name_field_remove');
}

add_action( 'wp_enqueue_scripts', 'wpb_adding_scripts' );

You have to be careful about the path. If it’s not working at this point, you can view the page source of your register page, and search for “name_remove.js” – look at the path on that script line. If the path is wrong, tweak it in the function above (you might need to change the get_stylesheet_directory_uri() part, or the path part after it. You can check if the path is correct by clicking the link to the .js file in the page source. If the path is wrong, you will get a 404 error. If the path is right, you should see the script code contained in the js file. Fiddle around with the path until it’s correct.

At that point, you have hidden the fields with CSS, and populated the second hidden username / name field automatically with javascript. Test your registration / confirmation email etc to make sure everything is working. But you should be good to go.

Hope that helps someone. Thanks to the folks I cobbled this solution together from.