BuddyPress.org

would there be any code somewhere to hide pages unless an admin user?

Why Docs Tab is active in private group for users that are not member of it?
is it possible to hide it and make not accessible for nonmembers?

https://wordpress.org/extend/plugins/exclude-pages/

There are lots of CSS hooks so you can customize the look of your messages pages. It would be easiest to just use some creative theming and create the effect. You could hide most profile information/avatar using CSS.

Or you could also try creating a custom page template using the private messages loop and adjust the parameters to suit your needs.

https://codex.buddypress.org/developer-docs/custom-buddypress-loops/the-private-messages-loop-bp_has_message_threads/

`bp_is_active()` checks if a BP $component is active – not whether members are registered but not activated. The `bp_account_was_activated` function is used in the activate.php template but isn’t appropriate here I don’t think.

In addition to the BuddyPress Conditional Tags – https://codex.buddypress.org/developer-docs/conditional-template-tags/ – you might also look at WordPress Conditional Tags – https://codex.wordpress.org/Conditional_Tags – to see if there are any that will work for you.

P.S. I just saw your other post.

`
This occurs due to my BuddyPress Auto Group Join plugin. How can I hide the not-yet-activated members from appearing on the Group Members page?
`

It seems like it would be better to modify the plugin(s) causing the issue instead of modifying the BP code. Maybe the plugin developers can assist.

FYI: I put a more generic posting here (https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/how-to-hide-content-related-to-members-who-are-registered-but-not-activated/#post-85519) if the admins think this is too off-topic

Hello,
I’ve been working all weekend on this one and I just can’t seem to find an answer.

*//PROBLEM: Users that have registered but have NOT activated their accounts show on the Group Members page (…/[bpressdirectory]/groups/[groupname]/members/). This occurs due to my BuddyPress Auto Group Join plugin (link below). How can I hide the not-yet-activated members from appearing on the Group Members page?

**Failed attempt #1 (members-loop.php):

`

… [BUDDYPRESS CODE]

`

**Failed attempt #2 (members-loop.php):
`

… [BUDDYPRESS CODE]

`

Any idea where I went wrong?

WordPress 3.0.4
BuddyPress 1.2.7

Plugins:
– S2Member (http://www.primothemes.com/post/product/s2member-membership-plugin-with-paypal/)
– BuddyPress Auto Group Join (http://twodeuces.com/wordpress-plugins/buddypress-auto-group-join) – This

Modify header.php in your theme. I think it’s wp_list_pages or something like that which lists the pages. Use is_user_logged_in() for the if statement to choose when to display the pages.

@Tekuan_Coleman

Gotcha! Here’s how…
1- Enable “Hide Main Theme Nav”, “Add WordPress pages/menus”, “Add Buddypress components” and “Scroll with pages”.
2 – Go to “Sizes & Position” and adjust the “Overall navbar width” to the width of your template.
3 – Play around with “Vertical offset” and “Horizontal offset” until you get it positioned about where you want it.
4 – Save settings.
5 – Now go to “Appearance” > “Menus” and select the WP3 custom menu you want at “BP-WP-Navbar Menu 1”
6 – Click “Save” at “Theme locations” and “Save menu”
7 – Check your site and refresh a page.
8 – Repeat, lather & rinse until you get it “just right”.
9 – Have fun!

@dorothysulzmann –

No short cuts on jQuery – but it’s quite straightforward to setup a simple script like you’ll need: their site is good and full of useful examples: http://jquery.com/

show() and hide() are basic jQuery – and there are plenty of animation options you can apply.

Also, take a look in the WordPress codex re: wp_enqueue_script – their recommended way of loading javascripts.

@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