BuddyPress.org

@Staceyk18,

If you mean the buddybar (grey) at the top of the page, you can change it by going into:

wp-content>plugins>buddypress>bp-core>bp-core-adminbar.php

and

wp-content>plugins>buddypress>bp-core>css>admin-bar.css

If you want to add menus to the login bar, you’re better off setting up a bp-custom.php, this thread will have details on what to do (read thru the whole thread):

https://buddypress.org/forums/topic.php?id=2186#post-12003

Firstly I notice that your Avatar cropper javascript is failing on registration. Also looks like bits of your site are missing, and messing with the BuddyBar (sub-sub menus aren’t appearing on hover.)

Otherwise, it’s working the way you have it setup. If what you’re asking is “why doesn’t my home theme look like testbp.org” it’s because you didn’t change your active home theme in WordPress.

Not sure what’s up with your member theme though. Might be missing some files or have some funky CSS or JS somewhere. Haven’t really looked into it for you.

Lo.

> Why is it when I add a page to my WordPress site, it doesn’t show up in my BuddyPress navigation?

Because that’s just the way the default home theme is written. The items listed on that menu aren’t ‘Pages’ in the WordPress sense, anyway, so it makes little sense for the default, out-the-box BuddyPress theme to do that.

The bit of code you’d need to change (or to add in your custom/duplicate theme) is in header.php. Where you see:

<ul id="nav">

Add this underneath:

<?php wp_list_pages('title_li=<h2>Pages</h2>' ); ?>

Documentation for that function is at https://codex.wordpress.org/wp_list_pages

We’ve unhooked the current fns and hooked up our replacement fns. So far they do exactly the same thing as the current fns. We need the ability to decide who gets to see the menu item. I choose to create yet another fn to decide yes or no on blog creation.

function my_can_user_create_a_blog(){

if (is_site_admin())

return true;

else

return false;

}

That goes in bp-custom.php also. Ya, all it does is check if the current user is the site admin. I’m not sure what you mean by only letting ‘Admins’ create blogs. There are blog admins and one site admin. Everyone with a blog gets to have the wp role ‘administrator’. Not sure what you want so i’ve wrapped the logic in a fn so you can change it to whatever you like.

Now we need to alter our new replacement fns to skip the display of the menu items if that returns false.

In our my_blogs_setup_nav() there is a line like this:

bp_core_add_subnav_item( $bp->blogs->slug, ‘create-a-blog’ __(‘Create a Blog’,

‘buddypress’), $blogs_link, ‘bp_blogs_screen_create_a_blog’ );

We need to wrap it like this:

if (my_can_user_create_a_blog()){

‘bp_core_add_subnav_item( $bp->blogs->slug, ‘create-a-blog’Create a Blog’,’buddypress’), $blogs_link, ‘bp_blogs_screen_create_a_blog’ );

}

Also the function my_adminbar_blogs_menu() has code that looks like this:

echo '<li' . $alt . '>';

echo '<a href="' . $bp->loggedin_user->domain . $bp->blogs->slug . '/create-a-blog">'

. __('Create a Blog!', 'buddypress') . '</a>';

echo '</li>';

You need to wrap that the same way:

if (my_can_user_create_a_blog()){

..all that stuff..

}

Okay, putting aside the subdomain versus subdirectory issue for a second, you state that:

…the bp link in the menu works but where is says “disbale components using below form” nothing shows

It sounds like BuddyPress is not activated. With the 1.0_RC2 changes, BuddyPress is now considered a single WPMU plugin. You must first login to the WPMU backend as site admin and then go to Plugins > Installed and make sure that BuddyPress is activated.

Once it’s activated, a new menu group is created at the bottom of the menu tree called “BuddyPress”. You click on BuddyPress > Component Setup and you should see that all the BP components are enabled by default. It is in this admin screen where you can enable and disable individual components.

If you’ve already activated BuddyPress, then something is clearly wrong. Have you double checked to make sure that you copied all the BP component files and folders (minus the theme folders) into the /wp-content/plugins/ folder? Did you install the BP suite into the /wp-content/mu-plugins/ folder instead?

If the BP install locations and files are in their proper place, then I would recommend deactivating BuddyPress then deleting the entire BP directory and try reinstalling the BP plugin suite again and see what happens.

Here’s two functions that change the way the admin bar displays user blogs.

// sort array of blog objs by $blog->role according to the order of $blog_roles

// roles not included in $blog_roles array will not be displayed

function filter_blogs_by_role($blogs){

global $bp, $blog_roles;



$blog_roles[] = __( 'Admin', 'buddypress' );

$blog_roles[] = __( 'Editor', 'buddypress' );

$blog_roles[] = __( 'Author', 'buddypress' );

$blog_roles[] = __( 'Contributor', 'buddypress' );

$blog_roles[] = __( 'Subscriber', 'buddypress' );



// get roles

foreach ($blogs as $blog){

$blog->role = get_blog_role_for_user( $bp->loggedin_user->id, $blog->userblog_id );

}



// eliminate roles not in $blog_roles

foreach ($blogs as $key => $value){

if (!in_array($value->role, $blog_roles))

unset($blogs[$key]);

}



// sort by $blog_roles sequence if there are any left

if ($blogs){

usort($blogs, 'compare_roles');

}



return $blogs;

}



// i love php.net. stolen from php.net usort manual, user mkr at binarywerks dot dk's

// contribution for priority list comparision function.

function compare_roles($a, $b){

global $blog_roles;



foreach($blog_roles as $key => $value){

if($a->role==$value){

return 0;

break;

}



if($b->role==$value){

return 1;

break;

}

}

}

You can put those two fns in your bp-custom.php file. The fn filter_blogs_by_role() does the work and the fn compare_roles() is just a helper fn.

filter_blogs_by_role() takes the array of blog objects returned by the fn get_blogs_of_user() in the admin bar’s bp_adminbar_blogs_menu() fn. It first gets all the roles for the user’s blogs and then removes all of the roles that are not listed in the $blog_roles array. That way you can eliminate some roles such as ‘Subscriber’ if you want. Next it sorts the blogs by the sequence of roles defined in $blog_roles. However you list them in that array is how they will display in the admin menu.

1) So, put those two fns in bp-custom.php

2) Arrange the roles defined by $blog_roles in the fn filter_blogs_by_role() however you want the roles to appear in the menu

3) Comment out the roles you do *not* want to appear in the menu

4) Put the call to filter_blogs_by_role() on line 133 in bp-core-adminbar.php like this:

if ( !$blogs = wp_cache_get( 'bp_blogs_of_user_' . $bp->loggedin_user->id, 'bp' ) ) {

$blogs = get_blogs_of_user( $bp->loggedin_user->id );

wp_cache_set( 'bp_blogs_of_user_' . $bp->loggedin_user->id, $blogs, 'bp' );

}



$blogs = filter_blogs_by_role($blogs);

Just in case the forums trash the code I also stuck it here: http://pastie.org/445729

There were some changes to the header.php file. Off the top of my head, I cannot remember if both the buddypress-home and buddypress-member themes had changes. Or, if only one of them had changes.

Either way, the best thing to do is open your header.php file and compare it to the new header.php file of the respective BuddyPress theme.

If I have the Blog-Menu in my theme – the bp_home_slug doest point to the right page (the home-blog) but to an article in another blog…

It should be BP_HOME_BLOG_SLUG, not BP_HOME_SLUG.

Hi Tutsie,

This type of change would typically be done with a plugin. Keep in mind that this isn’t a BuddyPress customization as much as it is a WordPress MU one.

I did a quick Google search for “change wordpress admin profile link” and found a few places you could start.

In this WordPress forum topic is some code that would change the behavior of the profile link (albeit for a different reason); this method of changing the admin behavior isn’t recommended, however, since it requires hacking a core file. A plugin would be much better since it doesn’t require changing the core file (and having to stress about updating your WordPress MU code later).

Depending on how much you want to work on this, you could download these two plugins: WP Hide Dashboard and Admin Menu Management, open them up in a text editor, and look at how they change the menus in the WordPress admin area.

Plugins do two things: (1) they provide a new functionality and (2) they hijack the normal WordPress behavior and perform the functionality described in the plugin instead.

Hope that helps…

Take a look at your admin menus for BuddyPress and Site Admin.

If you are running an older version of BuddyPress (before revision 1311) look in Site Admin -> BuddyPress. Otherwise the latest trunk has a new top-level menu called BuddyPress (look in General Settings).

View an example of the avatar menu.

And… this probably isn’t a support topic, right?

In your theme look for header.php. There you can change the names of the links.

For example:

<?php _e( \’Blog\’, \’buddypress\’ ) ?>

Change it to

<?php _e( \’My Blog\’, \’buddypress\’ ) ?>

Remember to change it in your members theme too.

Note that this will only change the text not the actual link. So it will show [My Blog] but it will still go to yoursite.com/blog

lol Oh Ren… haha!

@brandtd, this is certainly possible. As a matter of fact, this should happen as default unless you change the width of the body or html elements themselves. This is because the “Buddy Bar” isn’t contained by anything that has a relative position attached to it.

In bp-core/css/admin-bar.css – Try…

#wp-admin-bar {

position: absolute !important;

top: 0 !important;

left: 0 !important;

width: 100% !important;

z-index: 1001 !important;

height: 26px !important;

color: #fff !important;

text-align: left !important;

background:url(../images/admin_bar_back.gif) #818181 repeat-x !important;

}

@brian, duh I get what you’re saying now. If I can give some feedback about the Buddy Bar for a moment, I feel that it should be an all or nothing kind of deal. Either it’s always there for people to use, or it’s never there and people have to naturally find their profile area and do things from there. Toggling a whole new set of what are essentially just short-cuts and adjusting the entire layout of the screen, even if by 26px, provides for a moment of awkwardness from a user perspective. For the 3 seconds it takes for someone to think to themselves “Hey what’s that? Do I need it? What does it do? Oh gosh there’s tons of menus now? What is this stuff?”

Now if you’ve used WordPress.com or signed up for a Gravatar before, then the bar idea isn’t new. But for what I consider the core crowd we’re catering to by using BuddyPress as a social networking platform, if it isn’t uniformly worked into the design of the site from the beginning, it only serves to confuse.

Again, this is just my opinion. Not saying it’s right, and certainly not saying that there is a better way. Just saying…

/rant

Back on topic. In theory you could put a…

<body>

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

<div id="buddy-bar-buffer"></div>

<?php }?>

In your header file, and attach the CSS to that, rather than to the body itself? That would then only show that buffer when the user is logged in, and once they are logged in, that buffer will push the body down (as styled by the CSS you will give it in your base.css).

Does that make sense?

sgrunt, works like a charm for me! Thanks. Can you post this in trac for everybody please? Just those two changes to those elements.

https://trac.buddypress.org/newticket

As far as I can see these can be changed in

member-themes > buddypress-member > header.php

Search for id=”nav” around line 39

Would be good to have a language file for these elements.

Mike the idea is that if I want to change the function of a menu item, I have to replace the menu item with something of my own. I want to change “My Account” on the bar and add a new item underneath entitled: “I Owe Mike How Much!?”. I have to replace the entire “My Account” menu item since the granularity of the actions are at the top level menu item only.

I can slide new menu items in between existing items easily but that’s the way it has to happen for drop down items.

I create a plugin that runs in /mu-plugins since I want this to run all the time for all users on all blogs. It’ll get run every page load.

An example is replacing the bp logo image in the bar. Same technique for other menu items. The item gets rendered through the function:

bp_adminbar_logo() in bp-core-adminbar.php

This function gets registered in mu by us telling mu about this function and when to trigger it:

add_action( ‘bp-adminbar-logo’, ‘bp_adminbar_logo’ ) at the bottom of bp-core-adminbar.php

To replace the logo with our own logo or do something completely diff like just use the word ‘Home’, whatever we unregister the existing fn, register our own that replaces the old fn and does something different. Like below:

function oci_adminbar_logo() {

global $bp;

echo '<a href="' . $bp['root_domain'] . '"><img id="admin-bar-logo" src="' . apply_filters( 'bp_admin_bar_logo_src', site_url( MUPLUGINDIR . '/common-interest/images/oci_home.gif' ) ) . '" alt="' . apply_filters( 'bp_admin_bar_logo_alt_text', __( 'BuddyPress', 'buddypress' ) ) . '" /></a>';

}



remove_action('bp-adminbar-logo','bp_adminbar_logo');

add_action('bp-adminbar-logo','oci_adminbar_logo');

The above says “don’t pay any more attention to the function bp_adminbar_logo() when the action ‘bp-adminbar-logo’ occurs, pay attention to my oci_adminbar_logo() fn and do that instead.

You have to replace the *entire* menu item with something of your own. Clearer? No?

I honestly don’t know where all the instances for this is (plus “wire” appears in the urls, etc.). First start would be checking out the bp_wire_setup_nav function in bp-wire.php file in mu-plugins.php. That at least would change the menu names. Then I would imagine you would have change text in the BuddyPress user themes…

Hi wardeh. I was checking the ‘topics with no replies’ and saw you here. All by your lonesome self. How goes the battle this week?

You don’t want to turn off groups but you just don’t want the option to create more groups to be available. Well, you want group creation to be a site admin thing only. Hmmm…

I went and looked at the member theme code and finally arrived in the core code and lo and behold Andy was thinking of you! There is an unused option for the menu items. ‘site admin’ only. You’ll have to modify one line to turn off the group creation option for everyone except you.

In the file /mu-plugins/bp-groups.php at line 205. This currently reads:

Change that line to read:

That change adds the ‘true’ parameter at the end which normally defaults to ‘false’. It’s the ‘site admin only’ sees this menu item flag.

Merry Christmas.

Mike: if you are gonna mod the adminbar may I suggest this? A plugin that does the work for you without modifying the admin bar code. Andy made some changes to the adminbar to make it possible to replace menu entries easily and add new menu items between existing menu options. I use a plugin to do this. Used to modify it every time a change came thru SVN and got tired of that.

Here’s what I use:

http://pastie.org/344208

That’s a link to the code for a little plugin I use. What that does is it adds a new top level menu item ‘Community’ with the News, Members and all the other items that are available in the home and member themes as buttons.

You’ll need to modify this for your needs but it’s an example of how to add a new top level menu item and all the drop downs. The function oci_get_community_blog_url() goes out and gets some site options I have installed in my root blog theme. I don’t run the home theme on the mu root blog. I run it on community.ourcommoninterest.org. That menu gives access to the ‘community’ directories and recent activity. All the bp home theme stuff.

More on the adminbar in this ticket: https://trac.buddypress.org/ticket/174