The code above that goes in bp-custom.php blocks only buddypress specific pages from being viewed by logged out visitors. The plugin should block the wp post and pages. the bp-custom.php with the code and the plugin can be used together to block everything from logged out visitors.
http://www.mediafire.com/download.php?u6oos92g344485f
This plugin does not hide the activity tab in the main nav or in the profile activity tab but it does make activity friend only unless your the admin in which case it shows sitewide activity. To test it you would have to create two accounts that are not admins and not friends and put come activity in on both and you will see that as long as your not friends you can not see the others activity.
@medemlooper It just does not work, is there an error in the syntax, did you forget the add action below the function? Just curious because I can not get it to work. I wish there was an easier way to do this because It would be awesome. Please help I am stuck and I have done just about everything I know to do to get this going!
@modemlooper I’ve done you instructed and everything I know to do. I put the github code in bp-custom.php and I put your other code which calls it within the header div in header.php and it doesn’t spit out anything. I just don’t know where I am going wrong! This is all in my child theme WP 3.5.1 and BP 1.6.4
@modemlooper I used the code you supplied on gethub and I put it in my child themes functions.php between opening and closing php tags. Then I placed bp_notification_badge() within opening and closing php tags in the header.php just under the div id=”header” and nothing shows up at all. What have I done wrong?
@modemlooper I put the code from the gethub link in my functions.php and I placed
in the header.php after the and I can’t seem to get this to work, any help is greatly appreciated!
@modemlooper I am interested in using this too! Just for clarification would you place the function in the link you provided https://gist.github.com/modemlooper/5042788 in functions.php in my child theme then edit the header.php and then add as a li item in the menu or somewhere else in the header.php? Then style it in the style.css. Thank you!
Actually what I meant to say is that a child theme is not required but if your modifying your theme files whether it be the “Responsive WordPress Theme” or some other wordpress theme to work with buddypress then my instructions are correct. @modemlooper your great but it is still best for people to make child themes even with BP 1.7 beta 1. Reason being for example is when they update their particular theme from wordpress or they made a lot of changes in the child themes style.css, header.php, or footer.php etc. In any other instance then I am correct. my case it was a plain Jaine wordpress responsive child theme and it work perfectly! We can’t discount the value of a child theme for update reasons so we need to get clear on this! Maybe I suppose with the compatibility layer it is now a wordpress.org issue but people do need to be aware of it when installing buddypress because its a little different now but its not rocket science either!
You could talk to the theme authors and maybe they will help simplify the process otherwise you will need to make the adjustments using a tool like firebug for firefox to target the elements. If you have made a child theme then you can add the adjustments to the style.css so when your parent theme is updated the adjustments you made will remain intact.
And one other thing if you did this right you do not need a page called community, the community nav item is just a place holder for all your buddypress page links. When you hover it clicking community will not do anything but clicking its subnav items will take you to the buddypress pages you want in the subnav, subtle but effective.
By the way when you created the custom menu you did not need to parent anything in the buddypress pages. The custom menu does this when you nested those pages in the custom menu screen in the dashboard.
Here is a trick, when you create a custom menu as you have then create a dummy link url under custom links and label it “Community”. Add this to to custom menu drag it to the top above the other buddypress menu items, delete the dummy url in community you created and nest the rest of the buddypress menu items under it by dragging them in to the right so the are nested under the community menu item you created. Save menu! Works on my installation, and about 30 others I did.
@modemlooper its not required for the buddypress side of things but it is for the wordpress theme updates side of things unless you wanna loose the changes you may have made to the header.php, footer.php, functions.php, style.css etc.
@modemlooper But what if you have a wordpress theme like The Responsive Theme for instance and you want to make drastic changes to it. Wouldn’t it still be a better idea to make child theme? When I say child theme I mean just basically making a child theme for a wordpress theme not a buddypress theme.
As long as you make a child theme of the theme you are using with BP 1.7 beta 1 then the style.css and functions.php should still be fine when 1.7 is out. Since 1.7 has the compatibility layer building a child theme for a regular wordpress theme is all you need to do but if your going to modify any of the buddypress templates you will need to copy over
yoursite/wp-content/plugins/buddypress/bp-templates/bp-legacy/buddypress into the root of your child themes folder.
