BuddyPress.org

@ronia I completely agree with you. Now, I am a big fan and supporter of BP, its team and all of their efforts. I hope none of these comments are taken as being unappreciative of what’s been done. I will add, however, that IMHO what keeps BP from going from good/great to amazing is the lack of event & media capabilities into core. It’s just too important and, sadly no one has stepped in to fill the breach. The plugins mentioned cannot be called serious efforts because of their glaring holes. BP-Media is vaporware and has been for years. Buddyvents is damn near close but needs updating. Keep waiting is the best answer that can be given.

You should set up WP fully first checking all aspects of a standard WP install work correctly, when that checks out proceed to activating BP and doing so with the default theme initially to establish BP is set up correctly and working fully only them move on to activating a third party theme.

you can use my fork of bp album it works on 1.7 https://github.com/modemlooper/BuddyPics

Do you want it to be hooked to the main menu of the bp-default theme when a user is logged in ?

@hnla ok, I understand.

@bphelp thanks you very much mate 😉 just that i need !!
everybody suggest a plugin but its not necesary. adding code is the best solution.
thanks again 😉
kind regards

Are you doing it on a live site? Is your Theme BuddyPress compatible. For BuddyPress 1.6.x, the BuddyPress features are only available to BuddyPress enabled theme. In BuddyPress 1.7, BuddyPress automatically supports all themes(but 1.7 is still in beta and not recommended for live site).

Add this to bp-custom.php https://codex.buddypress.org/developer/customizing/bp-custom-php/
and it will prevent non-logged in users from accessing BP pages.
`
/* Block BP Pages For Non-Logged In Visitors */
function bp_block_pages() {
global $bp;
if ( bp_is_activity_component() || bp_is_groups_component() /*|| bbp_is_single_forum()*/ || bp_is_forums_component() || bp_is_blogs_component() || bp_is_page( BP_MEMBERS_SLUG ) ) {
// add components to be blocked to non-logged in visitors
if(!is_user_logged_in()) {
wp_redirect( get_option(‘siteurl’) . ‘/register’ );
} // Change /register to the page you want non-logged in visitors directed to
}
}
add_filter(‘get_header’,’bp_block_pages’,1);
/* End BP Blocked Pages */
/* Remove RSS Feeds */
function bp_remove_feeds() {
remove_action( ‘bp_actions’, ‘bp_activity_action_sitewide_feed’, 3 );
remove_action( ‘bp_actions’, ‘bp_activity_action_personal_feed’, 3 );
remove_action( ‘bp_actions’, ‘bp_activity_action_friends_feed’, 3 );
remove_action( ‘bp_actions’, ‘bp_activity_action_my_groups_feed’, 3 );
remove_action( ‘bp_actions’, ‘bp_activity_action_mentions_feed’, 3 );
remove_action( ‘bp_actions’, ‘bp_activity_action_favorites_feed’, 3 );
remove_action( ‘groups_action_group_feed’, ‘groups_action_group_feed’, 3 );
}
add_action(‘init’, ‘bp_remove_feeds’);
/* End Remove RSS Feeds */
`

@billgates82 you should always start a new post rather than tack onto an existing one that may seem to cover the same issue.

As in the post above yours consider looking at the S2 member plugin.

hi to everybody;

I have a BuddyPress Community that I’m building that’s based around a rather sensitive topic for my users and as such I need to make parts of the community totally private and not accessible by non logged in users.

I would like guests to be redirected to a page/message that requests login/sign-up before proceeding to the following parts of my community:

mysite.com/members
mysite.com/activity
mysite.com/groups/

However, I like guests to be able to freely view public blog and public content.

Is there a way to accomplish this?

You will need to configure BuddyPress before it comes into action.

Look for the notice in the Network admin. If it is not there, just click Network Admin-> Settings->BuddyPress and you should see the configuration wizard.

Hope that helps.

Hi,
Have a look at this function

bp_core_get_notifications_for_user here https://github.com/buddypress/trunk/blob/master/bp-members/bp-members-notifications.php#L83

You can modify it to suit your need(this is the one that generates the notfication messages).

and here you can see how the drop down is created
https://github.com/buddypress/trunk/blob/master/bp-members/bp-members-buddybar.php#L18

Hope that helps.

@p2ab BuddyPress does not work on installations where you give WordPress its own directory per your link above https://codex.buddypress.org/user/before-installing/#system-and-server-requirements

Are you saying that you want the notifications to be on the left side next to “My Sites”?

@ljvd – If you can wait a little while, BuddyPress 1.7 will work with pretty much any theme in the world.

That said, the default BuddyPress theme has a pretty solid fluid width that scales well for mobile. It is a great place to start, plus you can rest easy knowing that it is well-supported!

@unsalkorkmaz please note that I have edited one of your posts above. No personal remarks/attacks are allowed in this forum.

I appreciate that you want to give users as many features as possible with your theme and I understand your frustration. Having said that, the WP Theme Review Team Admin already noted which he considered plugin territory starting here https://lists.wordpress.org/pipermail/theme-reviewers/2013-March/012183.html and more so for the TinyMCE buttons later on the thread.

I supported you in the Author URL in the same thread. While I don’t agree with the TRT Admins 100% of the time, I support them 100% in the above-mentioned plugin-territory discussion. My unsolicited suggestion is to remove the items listed above which are considered plugin territory from your theme and create a plugin specifically for the theme e.g. Firmalite Theme Booster or Firmalite Add-ons or whatever you want. Further suggest submitting a revised theme while your theme is still up in the review queue.

Firmalite is the 13th in theme review queue as I write this. We’ve cleared many of the backlogs the past week and there are reviewers doing some reviews this week. Know that all of the reviewers are volunteers and also know that way sometime ago the waiting time for a review was 3-4 months.

Thank you for your patience.

The simplest ( and imo only viable ) approach would be an app wrapper.
All it does is launch the site in a browser.
Use of a wrapper is usually done just so that an app store listing can be created.