BuddyPress.org

@questus5

Look at your bp admin section, you will see the custom profile link you use that to create new groups and fields, as long as a new group is created under the ‘Base’ level then it will appear on the registration page.

@dorothysulzmann
As a workaround I would move the three type selections labeled ‘Fan off’? to just after the primary details and use the tree types as just that to confer a user type to each member but also run a simple jQuery show/hide on the further groups so all are hidden and then a check is performed to catch the radio selection and the appropriate group revealed with perhaps a ‘none’ control selection default.

The proper approach would be to complete a section and then pass the form control fields in a session or buffer to the next view to complete further sections but with BP that will likely start to get complicated, as techguy says there is no quick easy way to do this but with client side scripting it wouldn’t be that difficult.

1. Could you set this as a profile field ? For ex. A dropdown list added to the registration page where they state yes or no to a question on hospitality. If they answer yes they can be autojoined to the ‘yes’ group so everyone will know where to look for them.

2. If you are running a WP multisite you could set up a blog called ‘work listings’ or something like that, allow everyone ‘author’ capabilities set up one page as a standardized form and another to show the results of the posted form set the excerpts to show 0 -zero- characters and you’ll have a multipost page with a listing of jobs. – There are a number of plugins that will autojoin users to specific blogs on a multisite –

3. Same thoughts as with 2.

5. If you do a search for plugins there are a few that offer events calendars. Right now I’m using ‘My Calendar’ which offers an easily customizable interface so that you can make it look like your main site.

7. A simple page with a ‘donate’ button linked to paypal or whoever

8. WP multisite does this. If you set it so that users can create a blog on registration they can name the blog anything they like, I don’t know if you can automate the process so that the blog-name field is pulled from their username, or you can have a strict naming policy, add some text to the reg form stating that only the username is acceptable for blog names and set the joining process under moderation so that you have to approve each that way each blog will be called registeredusername.mydomain.com for subdomain installs or mysite.com/regusername for sub directory install.

4 & 6 I have no idea.

As for the plugins most come with the ability to activate either for one blog or for network activation, using the plugin ‘exclude plugins’ you can hide the plugins from your users blogs or allow certain plugins but disallow others. For ex, I have a user that wanted the plugin ‘ephemeris’ on their blog, I installed it, allowed it for that site and they are now happily ephemerising awaywhilst other users aren’t even aware that the plugin exists (they don’t see it on their blogs)

The plugins that I’m using I pulled straight from the WP plugin pages and so far they have all worked on my WPBP site without hiccup,

Regards.
Me.

I think €100 is well worth it for a good plugin. If the plugin means I can save a lot of time and get the results I need immediately, then yeah I’ll happily pay. My time and frustration are worth money too. If he spends 20 hours developing a plugin and I buy it for €100, I think I just got a great deal!

I find this JobBoardr plugin particularly interesting because we had a similar plugin written for our site, easyoutsource.com. It’s a job hiring site for Americans to hire people in the Philippines as online workers. The big issue, as you’ve already discovered I’m sure, is how to separate the roles. We set up a custom field for workers and one for employers and made you pick your role on signup. The role is just a profile field you select on signup. Then on the site every function is dependent on which role you picked. Groups have been turned into jobs entirely. Employers can create groups and workers can apply to them. Another big issue we had was that employers always showed up in the search results. We wanted to display workers (members) and jobs (groups). No employers. So we had to get a custom plugin written (by the ever so talented R-a-y) to hide employers from search results.

It’s interesting that you’ve set it up so that employers ARE groups and workers are members. Are your employers not also members? Do they have their own profile pages? How did you get this to work correctly?

.You could also try my plugin (he says with shameless self-promoting grin).

See this post for the latest beta version: https://buddypress.org/community/groups/add-all-nav-links-to-bp-adminbar/forum/topic/updated-the-beta/
Here are the user configuration options available in the admin panel under “Settings” > “BP-WP-Navbar”
– Hide or display the main theme navigation
– Hide or display the site name in your new adminbar
– Hide or display the Login and Signup links in the adminbar
– Hide or display the “Visit Random” menu
– Select whether to display top-level WordPress pages horizontally or in a dropdown menu
– Define the label for the dropdown in WordPress 2.x
– If you’re running WP3.x, the plugin will fetch whatever custom menu labels you assign and display them in the admin bar along with all child pages in dropdowns
– Define the label for the Buddypress directory dropdown (default = “Community”)
– Define the font, font-weight and font-style for all menu items
– Define ALL colors: navbar background, main and sub menu item backgrounds, border, text and hover colors too
– Set the overall width of the navbar and of sub-menus
– Set the height of all menu items
– Adjust margins where required
– Reposition your fancy new custom navbar anywhere you like, relative to your theme so it scrolls with your pages

If you add categories to your custom menus in WP3.x, the plugin will pick them up and display them in whichever menus they are assigned to. Give it a whirl.

@jenyus

Here comes some shameless self-promotion! Try the beta-version of my plugin: Add-All-Nav-Links-To-BP-Adminbar. You can add all your main navigation items to the bp-adminbar, hide your theme’s main nav, then customize your new adminbar just about any way you like, including repositioning the whole thing anywhere on your pages. Here’s a screenshot of the backend admin panel: http://i33.tinypic.com/2nvea8j.jpg

You can download from my site here:
http://nowrecovery.com/downloads/add-all-nav-links-to-bp-adminbar2.1beta.zip

The current release is available here:
https://buddypress.org/community/groups/add-all-nav-links-to-bp-adminbar/

If you try it, please let me know what you think in the plugin’s forum

Are you asking if there is a way to have a user’s friends only available to him or her? Adult dating sites and consulting groups/companies find the end users like a layer of privacy that doesn’t let site users see their friend connections. I dont know if it can be done in buddypress.

You could go line by line through the theme to remove pages that display friends, but I’ve never tried to see if it would work.

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.

@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

Add to your theme’s style.css
div#item-header span.activity { display: none; }
This will also hide same in Group’s pages

Edit – ok @hnla that was fast

You could probably hook into the get_header action, do your conditional check and if the person is a mentor, then show the page, otherwise show the registration page or whatever.

Modify the function listed in this thread:
https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-make-a-private-community/?topic_page=2&num=15#post-44616

Hopefully it gives you a few pointers.

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 …

this plugin hides every pages ton non-registered users
https://wordpress.org/extend/plugins/registered-users-only-2/

this one can hide specific pages / components
https://buddypress.org/community/groups/s2member/

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.

Hi MrMaz, I think your plugin is super! I do have one question, we are building a buddypress pay site and we want to hide all of the tabs except for a few pages if the user is logged in. Where can I find the code that creates the “Links” navigation in the top header so that I can hide it if the user is logged in or not? Also, can “Links” navigation item be changed to the word “Videos” instead? It seems like both of these would be easy fixes once I knew where the code is, or is it more complicated than that? Thanks in advance for your help!

Here is my Sidebar which does exactly what you want: Show different sidebars on different BP sections of the site.. It does not work 100% (blog sidebar does not show up yet) but it should get you started. You use BP conditional tags to show/hide the different sidebars depending where the user is on the site:

<?php do_action( 'bp_before_sidebar' ) ?>



<div id="sidebar">



<div class="padder2">

<?php

locate_template( array( 'accordeon.php' ), true );

?>

<?php do_action( 'bp_inside_before_sidebar' ) ?>

<?php if ( is_user_logged_in() ) : ?>



<?php do_action( 'bp_before_sidebar_me' ) ?>



<?php endif; ?>



<?php /* Show forum tags on the forums directory */

if ( BP_FORUMS_SLUG == bp_current_component() && bp_is_directory() ) : ?>

<div id="forum-directory-tags" class="widget tags">



<h3 class="widgettitle"><?php _e( 'Forum Topic Tags', 'buddypress' ) ?></h3>

<?php if ( function_exists('bp_forums_tag_heat_map') ) : ?>

<div id="tag-text"><?php bp_forums_tag_heat_map(); ?></div>

<?php endif; ?>

</div>

<?php endif; ?>



<div class="padder3">



<?php if(bp_is_group()){

if(!dynamic_sidebar("Group Sidebar")){?>

<?php }

}

else if(bp_is_member()){

if(!dynamic_sidebar("Profile Sidebar")){ //if user profile etc

?>

<?php

}

}

else if(bp_is_blog_page() || bp_is_directory()){

if(!dynamic_sidebar("Blog Sidebar")){?>

<?php } }

else dynamic_sidebar( 'Sidebar' )?>

<?php dynamic_sidebar( 'sidebar' ) ?>

</div>



<?php do_action( 'bp_inside_after_sidebar' ) ?>

<?php /* Show forum tags on the forums directory */

if ( BP_FORUMS_SLUG == bp_current_component() && bp_is_directory() ) : ?>

<div id="forum-directory-tags" class="widget tags">



<h3 class="widgettitle"><?php _e( 'Forum Topic Tags', 'buddypress' ) ?></h3>

<?php if ( function_exists('bp_forums_tag_heat_map') ) : ?>

<div id="tag-text"><?php bp_forums_tag_heat_map(); ?></div>

<?php endif; ?>

</div>

<?php endif; ?>

</div><!-- .padder -->

</div><!-- #sidebar -->



<?php do_action( 'bp_after_sidebar' ) ?>

Make sure to register the sidebars in your functions.php (of your child theme)

if (function_exists('register_sidebar')) {

register_sidebar(

array(

'name' => 'Blog Sidebar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Profile Sidesbar',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Group Sidebar ',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Left Footer',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Middle Footer',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

register_sidebar(

array(

'name' => 'Right Footer',

'before_widget' => '<div id="%1$s" class="widget %2$s">',

'after_widget' => '</div>',

'before_title' => '<h3 class="widgettitle">',

'after_title' => '</h3>',

)

);

}

So many posts about this topic!!!

I too want to restrict pages / posts / and ALL buddypress pages to non members …

Thanks peterverkooijen for the temporary solution but there should be a plugin that can do this in a nicer way.

Does anyone know?

I just wanted to add my own low-tech solution to a similar situation. This is what I did to hide all my BuddyPress features (members, activity, etc) while keeping my pages and blog posts publicly accessible…

In my child theme, I copied the members/index.php, activity/index.php(etc etc) folders and files. Then in the index files, I surrounded everything inside the “padder” div (which displays all the content) with a is_user_logged_in tag like this:

<div class=”padder”>

<?php if (is_user_logged_in()){ ?>

(content guts go here)

<?php } else { echo “<h3>Members Only!</h3><p>Sorry. The page you have requested is for registered members only. Please visit our About page for more information on member registration. Thank you for visiting.</p>”;} ?>

</div>

PHP isn’t really my thing, so that’s probably not the best way of doing it, but it worked.

It’s not any one plugin that does the job. Here’s how I do it.

Create a new blog (let’s call it Test) and set the privacy (more privacy options needed here and bp-mpo-activity-filter to keep it’s content out of the stream) to “only blog admins can see this blog” (this is necessary, but keeps things clean since nothing should get added to this blog).

Use new-blog-defaults to set the blog defaults including menus that the users cannot use.

Members is used to set capabilities of the admin (I don’t change the role of the new blog just the admin’s capabilities) so the admin is “like” an editor or author, but I can still let them change their themes (theme changing is very important to young users).

Wpmu-plugin-manager lets you set which plugins to allow users to use and which ones are automatically turned on (I always turn on Ozh’s Admin Menus for example). Turn on any plugins you want to use and tweek their settings and any other blog settings.

Then Adminimize to further hide menus the users don’t need (it only hides menus, but most users will never find them anyway). Adminimize is great for simplifying the write panels for posts and pages too. Any plugins I don’t want users to change settings on I can make sure they don’t have access to by making sure the menus are hidden.

Now use new-blog-options under the site admin menu and give it the blog id of Test and check off any of the database fields you want new blogs to have (make sure the Members and Adminimize ones are checked). Maybe this isn’t exactly what you want, but it is probably the best overall way to simplify blogs for younger users.

Also since I use these with classes, I just import my whole list from a spreadsheet using DD Import Users as subscribers on the main blog. I use limit-blogs-per-user and set the site-admin/options to 2. Now users can create their own blog, but can only create one blog of their own. This saves me a lot of time, but still gives the users a fair amount of freedom with their blogs.

It isn’t a perfect solution. I would like to see some of the overlapping capabilities put into one plugin for cloning blogs. I would especially like to see the ability to have different templates (ie base blogs to clone from) so that I could have one setup for say grade 1 students and another setup for grade 5 students.

Hope this is useful to someone.