BuddyPress.org

@hnla Well now, great progress!

I remember writing at some point that it’s often the most obvious that escapes me… Turns out I hadn’t “actually” selected any files to upload to subversion… I was just going through the motions and clicking buttons (doh!). The first version of the plugin is up and I just updated it with a whole bunch of cool new stuff. Code here: http://pastebin.com/Qquwe9pH

Thanks to your examples, I created 3 new custom configuration options: in addition to hide/show the main nav, users can now choose to hide/show the site name/logo, the Login/Signup links, and the Visit Random dropdown. I’ve also completely revamped the readme with a detailed FAQ, and added a fully commented stylesheet with the rules I use for my site to help get folks started on customizing their new admin/navbar.

Thanks a whole bunch for your invaluable help and instruction on this project! I can now say I’ve popped my plugin cherry!

Now we just have to wait for subversion to update………

Good spot, that’s why second eyes are vital, also the $hideMainNav doesn’t need to be globally scoped as the function sits outside pages() and the variable is already in the main page scope so no global required for it.
Not sure how the process works for uploading plugins but would guess it hasn’t been approved yet?

If I have a minute I’ll add the config variable for ‘Community’ link then you can run things through their paces when your back.

new adjustments:
typo corrected;

http://pastebin.com/TA4vGHT5

Config section created at top of file – labels all set from that point by user

Hide main nav links function created to add embedded styles via add_action dependent on user setting $hideMainNav = true

Hiding the main nave through CSS isn’t really the best option as it leaves the markup there, it would be better to remove altogether you may want to change default to true(hide)

This is somewhat of a stopgap solution to user parameters.

As always check over thoroughly for any other typos I may have missed

@pcwriter

I’ve had to do a fairly extensive rewrite on the function for a number of reasons:

1/ There was a significant degree of malfomed ul child nesting which prevents drop down aspects working correctly primarily I’ve removed the opening and closing UL elements as they are not required and cause issues.

2/ Not sure how the wp_list_pages was intended to work but with the parameter ‘title_li’ declared as empty you correctly remove the wrapping elements but would need to add UL elements manually wrapping the function call for the dropdown to function correctly.

3/ Added back in the wp_nav_menu function calls but wrapped them in a check to see if WP 3.0 is running i.e are the new menu available if not hide altogether.

Also added a reverse check to remove the wp_list_pages function if using the new menus as there is little point in both and the new menu system serves better.

4/ Changed region and menu top link names to ‘pages’ but this area is a fundamental issue as it cant be known what the user sets as menu names, ideally one shouldn’t hard code values but retrieve them from the admin menu area, but this proves far too hard to work out (asked a question on WP support but haven’t had a reply and I don’t expect one – sadly there is little codex documentation of any depth on the new menus.)

This issue applies to the wp_list_pages as well as you can’t really pass any values for ‘include’ and ‘exclude’ as these values can’t be known so you ought to remove those values you have hardcoded (I have left them in).

If I can get some guidance on how to fetch values from the menu backend view such as menu names then it will be possible to make the menus far more effective but have spent quite a while trawling through the core WP files for nav-menu and it’s not obvious and too time consuming.

I have copied the revised code to this pastebin page, give it a check over, but don’t assume I have things all correct, run it as plugin copy 2

http://pastebin.com/trUDaPEP

There’s also WP Hide Dashboard: https://wordpress.org/extend/plugins/wp-hide-dashboard/

@jonnylons

Don’t know about the post, but here’s the plugin:
https://wordpress.org/extend/plugins/adminimize/

And that old post is located where exactly? Cmon people – share!!!

I was going to do the remove thing, too–so thank you all for the tips–but then I decided I might as well just hide the admin bar from logged out users, as that was my bigger concern with the random visit.anyway. (I don’t think it’ll be especially useful, and our groups are mainly private, but I don’t have any other plans for the top right portion of the screen, so…might as well leave it for now.)

@intimez – good info – thanks.

I also came across this code: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/removing-members-ability-invite-others-to-a-group/#post-48304

Which promises to hide the “invite friend” links (haven’t had success yet…)–

Or you can create a child theme that removes the links from your template… Though really, I agree the system should be more set up like this:

Public — anything goes
Private — only mods and admins can INVITE (not just approve)
Hidden — same as private – only others can’t see

Cheers

Hi, I too want a solution for the same problem just like you. I want to hide admin and sitemanager from the members list. I was searching everywhere for it. If you know something about it just send a message to me to my profile. Waiting for your reply…..Plz….

@marianbuchanan

Try this:
Dashboard – Buddypress – General Settings
Hide admin bar for logged out users?: YES

Try this plugin: https://wordpress.org/extend/plugins/adminimize/

I was having a hard time trying to find the .htaccess file on my iMac, until I figured out that it is a hidden file (I’m working on MAMP Pro). If that is your case (Mac) , you have to unhide it.

1. Did you change settings like BuddyPress > General Settings – Hide for logged out users?
2. Did you change your theme? Did you check if your new theme had wp_footer() in footer.php?

you could hide #bp-adminbar-notifications-menu via CSS display:none

@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 …