BuddyPress.org

Graphene Mobile Neo is a premium addon so it is hard for us to test it. What happens when you disable that addon? Does the uploader work? If not, you’ll have to look into debugging iOS Safari.

If you can duplicate this issue on a free theme, let us know.

You were correct. I switched to Twenty Seventeen, and it worked.

I’m using the Graphene theme, along with its special “Graphene Mobile Neo” theme for mobile.

Can I correct this problem by putting !important in front of some properties in avatar.min.css?
If so, which properties should I add that to?

Or if that’s not the solution, is there a better way to solve this besides switching to a different theme?

Thank you!

Can you try changing your theme to something like Twenty Seventeen?

Sometimes the current theme has CSS that conflicts with BuddyPress functionality.

What theme are you using?

I’ve noticed similar things myself.

Can you see if the following helps?

Add this code-snippet to wp-content/plugins/bp-custom.php file?

remove_filter( 'bp_email_get_property', 'bp_core_deprecated_email_filters', 20, 4 );

remove_action( 'bp_send_email_success', 'bp_core_deprecated_email_actions', 20, 2 );

The easiest way to do this is to edit the home.php file. You’ll need to comment out bp_get_displayed_user_nav() and the related markup.

Ref: your-child-theme/buddypress/members/single/home.php

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.

I would check out https://themeforest.net/search?term=buddypress
This will show all the premium themes that are made for buddypress.

I’ve had some good experience with buddyboss.

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

You can get the value of an xProfile field in BuddyPress quite easily but you will need to use code. Take a look at this article to get started:

Displaying Extended Profile Fields on Member Profiles

You can check if either of these two directories exist inside the theme:

• buddypress
• community

If either of these exist, the content inside is specific to BuddyPress and will likely be custom.

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.

@cameronjonesweb

Why are you unhooking the reg form from the content? I think the BuddyPress template hierarchy can help you here.

Template Hierarchy

You can just nuke the reg form from your-child-theme/buddypress/members/register.php and then add your custom form.

You’ll want to look at our template hierarchy codex page:
https://codex.buddypress.org/themes/theme-compatibility-1-7/template-hierarchy/
https://codex.buddypress.org/themes/theme-compatibility-1-7/template-hierarchy/#single-member-pages

Then, you could customize the layout of your member profile pages by adding a sidebar or whatever only on member profile pages.

You need to find out which theme template your My Profile page is using – maybe single.php.
You may need to make a custom template and remove the comments call from it.

In your child theme, you’ll have a style.css file. If you don’t then you can create one so your folder structure will look like this:

wp-content/themes/your-child-theme/style.css