BuddyPress.org

@davol Why are you using the bp-default theme by way of the template pack plugin, the whole thrust of BP 1.7 was to provide theme compatibility, template pack plugin ought to be considered redundant now for new sites/themes.

You should really remove those copied directories and the plugin and just let theme compat take over. If you need to modify templates then you copy them into /my-theme/community/members/index.php

*/community/ or /buddypress/

No they wouldn’t as you are working in a child theme.. aren’t you! if not you should be.

I’m not sure but scanning your post possibly suggests smething amiss in your understanding of BP, as modemlooper points out hiding fields is easy and along with the privacy controls on BP profile fields you can ensure that they are set to both required and only editable by admins so not sure why you need your custom form, but may have overlooked the reason.

You certainly don’t have to set up a localisation file if changing the odd heading in BuddyPress is all you need to do.

That said – The benefits of having a localisation file in place are huge (i can name some if you like..?) and it isn’t difficult to set one up if you follow the tutorial on that page.

Going back to your method of editing your theme’s files – try making the exact same change in file:

plugins/buddypress/bt-themes/bp-default/members/index.php

If that change works then you haven’t set up your child theme properly.

@inge12

https://codex.buddypress.org/developer/customizing/customizing-labels-messages-and-urls/

https://codex.buddypress.org/developer/customizing/changing-internal-configuration-settings/

?

The easiest way to inherit ‘some’ of the CSS from the default theme is to copy what you need and paste it into your theme’s style.css.

Then add this to your functions.php file

if ( !function_exists( 'bp_dtheme_enqueue_styles' ) ) :
    function bp_dtheme_enqueue_styles() {}
endif;

This will tell BuddyPress not to queue up the default stylesheet.

Instead of editing the text strings in the core or you theme’s files, you can use a language translation file. It makes life much easier:

https://codex.buddypress.org/developer/customizing/customizing-labels-messages-and-urls/

Has someone found a solution to this issue? I also want to deny access to non-logged in users to group and members pages.

I tried private_community_for_bp but I did not understand how to customize code since I want to leave generic users to vist 3 pages that do not belong to bp installation since, like site homepage

If you are checking for BuddyPress activation page, you can use any of the following

if( bp_is_activation_page() ) {
//do something
} 

or

if ( bp_is_current_component( 'activate' ) ){

//do something
}

hope that helps.

@jpc-solutions what have you done so far to resolve this? Have you tried changing to Twenty Twelve theme or BP Default theme to check if it’s a theme conflict? Have you deactivated plugins batch by batch except BuddyPress to check which is causing the issue?

Leofitz, WangGuard will check your user base for spammers and delete them.

See https://wordpress.org/plugins/wangguard/

The author says that “WangGuard not only protect your site from sploggers, spam users or unwanted users, WangGuard cleans your database from them. No plugin or service does this, only with WangGuard you will get this feature,” and I believe him. His English may not be too good, but the plugin is really outstanding.

There’s just one consideration for you: In order to have your database cleaned up, you will have to submit far more than 500 queries the first month. Perhaps you can arrange to pay for a month?

Here’s my suggestion to reduce database queries after that. (It worked for me.) Buddypress allows for the customization of User Profiles. Add a couple of questions that require a certain amount of intelligence to answer and make them required. That means the form will not be submitted either to WordPress or to WangGuard if the required fields are not filled out. It’s not fool-proof, but it decreased queries on my very busy site to just a few a day.

Incidentally, I added a question, “How do you plan to participate?” Among the choices offered the user are these:
“I want to increase my online presence.” and
“I want to sell my stuff.”

We don’t need anyone not bright enough to figure out that these replies do not make the user desirable. Now all I need is a script to automatically kick out users who choose these replies. 😉 (As it is, they can be manually deleted if other users report them.)

I don’t know what happens to a group when all the users are unsubscribed, so this may not be precisely what you are looking for. But WangGuard will make your site secure against almost all sploggers. (One registrant passed all tests on our site, and we had to delete manually, but that person must have registered manually too.)

Good luck!

Inge (http://ssnet.org)

Given that BP 1.7 introduced theme compatibility, and 1.8 will extend that considerably as we have now brought into play a new level of template hierarchy along with placement of assets CSS/JS in BP directories the question is moot, as you can do either but a child theme is always a child of whatever parent theme you have chosen to use – unless you decide to overload BP by adding bp directories directly to the top level of a theme in which case theme compatibility would be automagically disabled.

The rule of thumb is that if your chosen theme can be updated and you want to make custom changes to BP template files then you do so in a child of that parent theme, even if only containing the ‘buddypress’ ( or ‘community’ ) directory to ensure your changes are maintained in your own child theme.

@dswd depends on the project. If you’re creating a WP theme and want to make it compatible with BuddyPress, simplest requirements are: the_title() and the_content() and using jQuery which comes bundled in WP. That’s it. BuddyPress is compatible with nearly all WordPress themes.

@compassseeker
Add the code in the link below to bp-custom.php:
http://pastebin.com/HSpJNLyV
Also see @mercime ‘s replies in the following thread:
https://buddypress.org/support/topic/adding-dynamic-profile-link-to-main-menu-item/

@soloacademy
Covered this here:
http://bphelpblog.wordpress.com/2013/06/19/buddypress-redirect-to-profile/

While very doable, this will require custom coding.
You can contact me at PhiloPress

You need to state which versions of WP & BP you use.

You want to ‘hide’ the profile page for a member who hasn’t paid their dues?
What should happen if that page is accessed by that member or another member?
Redirect? Custom message page ?

If ‘paid dues’ is a boolean, then it’s easy to write a function.
Where is that boolean stored?

Does that member still appear on the Members page? In the Activity stream?

iow. you need to be more specific about the behaviour that you want.