BuddyPress.org

@damian2001, change to bp-default theme, you will see the bp-admin bar across all sites like the one at http://testbp.org/
Double check dashboard – BuddyPress > General Settings > Hide admin bar for logged out users?:> should be NO

No you’re not the only one I raised a ticket on the matter.

Problem is that for the moment you shouldn’t use that hide adminbar unless you make some changes. The issue is that there is a function that checks to see if disable adminbar is true and if so it generates a style tag with a ruleset to hide the adminbar with display:none, this function then adds an action with places this style tag erroneously in the wp_footer hook resulting in a style tag sitting in the document body, a major validation issue as it’s obviously illegal to place this tag at this point in a document.

As in reality this style tag is not actually required due to the adminbar being removed anyway the function ought to have been removed, but for some unknown reason it was deemed to be ok to leave until bp 1.3 branch is released.

To fix in the meanwhile as there may be a wait for 1.3 you will have to add a remove_action or edit the core file holding the function (not first choice)

In a child functions.php file you can try adding this line:

remove_action(‘wp_footer’, ‘bp_core_override_adminbar_css’);

That should prevent the action from running, tested and works for me on WP 3.0 BP 1.2..4.1, but there may possibly be better approaches?

I don’t think that’s the case.

You only have a blog if you’re the administrator of a blog.

Not sure what to tel you about the theme issues you’re having (I just modified the BP default one), but I get what you mean about the BP groups/forums confusion.

The audience I’m after is used to vbulletin forums, so I actually found some code posted here on BP.org that made groups open onto the group forum by default, and then I put a conditional around the activity stream posting thing on the group activity pages that only allows admins to see/use that. This way, all group activity id funneled into the forums, unless the group admin just feels the need to post something to the activity stream. I also just did away with the ability to post activity stream updates from the sitewide stream page, but you could just modify the ‘post update to’ dropdown menu there to hide and make it post to the user’s profile only.

All in all, I’ve found that Buddypress can be a bit of work if you want to change the way it does certain things, but for most people the features are worth the trade-off of some extra work. I hope you get it all figured out and working the way you’d like

@themeanwhile – you can enable or disable the various components so if you want Activities only, enable that and disable other components. After you activate BuddyPress, go to the new BuddyPress menu item on the left column of dashboard, and go to

a) General Settings – these are your choices
Base profile group name:
Full Name field name:
Disable BuddyPress to WordPress profile syncing?: Yes No
Hide admin bar for logged out users?: Yes No
Disable avatar uploads? (Gravatars will still work): Yes No
Disable user account deletion?: Yes No
Disable global forum directory?: Yes No
Disable activity stream commenting on blog and forum posts?: Yes No
Default User Avatar – For users without a custom avatar of their own, you can either display a generic logo or a generated one based on their email address

b) Component Setup
Activity Streams – Allow users to post activity updates and track all activity across the entire site.
Enabled Disabled
Blog Tracking – Tracks blogs, blog posts and blogs comments for a user across a WPMU installation.
Enabled Disabled
bbPress Forums – Activates bbPress forum support within BuddyPress groups or any other custom component.
Enabled Disabled
Friends – Allows the creation of friend connections between users.
Enabled Disabled
Groups – Let users create, join and participate in groups.
Enabled Disabled
Private Messaging – Let users send private messages to one another. Site admins can also send site-wide notices.
Enabled Disabled
Extended Profiles – Activates customizable profiles and avatars for site users.
Enabled Disabled

I would suggest you set up a test install so you can check the features for yourself.

“Of course, activity filters, profile page, friends page, settings page, etc, would also need to be migrated to display in the backend.”
Why? If you want to make the BP Activity section private, you can add conditional tags for is_user_logged_in …

If you rename it now ( usually rename it/ wp-content/plugins1) that will hide access to the plugins from the admin portion of your site. You would then be able to get to your site’s admin panel. Once you log in and reach your admin panel, rename the plugins directory back to /wp-content/plugins.

The problem is most likely with the last plugin you activated.

Socialpreneur has a nice snippet here that makes it easy to hide the admin from the members list assuming you know the admin’s login name.

Place this in your bp-custom.php:


function my_bp_member_user_login() {
echo my_bp_get_member_user_login();
}
function my_bp_get_member_user_login() {
global $members_template;
return apply_filters( 'my_bp_get_member_user_login', $members_template->member->user_login );
}


Then in your members-loop.php file, place this just below the while statement (wrapped in php tags!):
if ( my_bp_get_member_user_login() == 'admin' ) continue ;

(Supposing your admin’s login is ‘admin’.)

I use a Profile Privacy plugin created by http://www.jfarthing.com/. Sadly, the link to the plugin in my dashboard comes up 404 in the wp repositorty, and I can’t seem to find reference to it on his site. That said, the plugin allows for you to manage who can see certain fields in the profile (everyone, friends, user). When profile fields are set to “user” only the user and the site admin can view the info. Perhaps an attempt to contact jfarthing will met results. Good luck.

You still want to keep blogs, but want to hide it from the navigation correct?

Use CSS!
li#blogs-personal-li, a#bp-admin-blogs {display:none;}

Terrific plugin! Using BuddyPress Links 0.4.1 (with BuddyPress 1.2.3, WPMU 2.9.2). Some feedback:

Frontend:

– When viewing a link in the Links tab, the A tag of the external link icon needs a target=”_blank”.

– Would be nice to have “Report Broken Link” and “Flag as Inappropriate” buttons for each link (or may be simply “Report” to save space, and it popups to “Report Broken Link” and “Flag as Inappropriate”). Then have that status show up in the Manage Links page as two additional columns. And also have a way of filtering and showing just broken or inappropriate links in the Manage Links report. And also have a way to clear status. Perhaps record user who reported the status (in case that user is falsely reporting and should be banned).

Backend:

– Instead of 3 entries in the BuddyPress dashboard menu (i.e.: BuddyPress Links / Manage Links / Edit Categories), have only one entry “Links”. Then divide the admin page into tabs: Settings, Links, Categories, Support, About.

– The “Search Links” box and the “Search Categories” box (on the Manage Links and Edit Categories pages, respectively) are not in the same vertical location. “Search Links” box is above the heading, “Search Categories” is below the heading.

– Disable the “Delete” buttons if no Links/Categories selected to delete.

– When doing a search (Search Links / Search Categories), add a “Show all Links” / “Show all Categories” button/link to clear the search criteria.

Manage Links page:

– Make all the A tags (Details / Owner / Edit) have target=”_blank”.

– Link the link avatar to the destination URL (with a target=”_blank”).

– If hover over a link avatar, show full size image in floating popup (like a tooltip).

Settings:

– Have a setting to enable/disable rel=”nofollow”.

– Have 3 checkbox settings to hide a link if it: (1) goes below a specified negative rating (e.g.: -10); (2) is flagged inappropriate a specified number of times; (3) reported broken a specified number of times. The link’s owner would still see the link but with a warning.

– Have a setting to specify what avatar to show if none specified. First radio box would be “default avatar”, following by radio boxes to select screen snapshot thumbnail from the various snapshot website services.

You probably already tried this tutorial:
http://www.michiknows.com/2007/02/12/who-else-wants-to-hide-their-wordpress-admin-folder/

The other technique is hacking WP core files:
http://www.socialblogr.com/2009/09/how-to-change-folder-name-on-wordpress.html

You could also try applying a filter to “admin_url”, but when I tried this awhile back, it didn’t work:
http://stackoverflow.com/questions/2584706/wordpress-where-the-admin-url-is-set

I should note that I’ve never done this and strongly advise you not to as well.

—

WP should have a defined WP_ADMIN_URL variable similar to WP_PLUGIN_URL and WP_CONTENT_URL, but it doesn’t.

Easiest way to remove favorites is to use CSS:
li#activity-favorites, li#activity-favs-personal-li, a#bp-admin-activity-favs, .activity-meta a.fav {display:none;}

This will hide all favorite buttons and tabs (I think).

Your second, third and fourth requests can be taken care of by making sure the groups are set as Private. That means that they don’t show up in public listings, and their contents are only visible to members of the group.

In order to make sure that people can only be part of a single group, you’ll want to hide the Send Invite screen for all users, or at least for non-admins. You could either do this through CSS, or by modifying/reproducing the functionality defined at bp-groups.php groups_setup_nav().

As for the first question, there are WP plugins that allow you to restrict membership to invited members. A ten-second Google search turned up this: https://wordpress.org/extend/plugins/wp-invites/, for example. I imagine that this would work fine for BP as well. The most straightforward way to populate groups would then be for the admin to use a plugin like BP Group Management http://teleogistic.net/code/buddypress/bp-group-management/, which allows admins to place people manually in groups, bypassing the invitation process.