BuddyPress.org

@acaps2007
What I’ve found finally:

(It’s based on this article:
http://easyoutsource.com/blog/how-to-code-a-custom-adminbar-in-buddypress/)

So if you just set your adminbar to be hidden in css rather than completely disable it in the wp-config.php, you could use to call the notification menu.

If you’ve completely disabled adminbar, then use the following code instead(it’s copied from bp-core-adminbar.php):

<?php
global $bp;

if ( !is_user_logged_in() )
return false;

echo '<li id="bp-adminbar-notifications-menu"><a>loggedin_user->domain . '">';
_e( 'Notifications', 'buddypress' );

if ( $notifications = bp_core_get_notifications_for_user( $bp->loggedin_user->id ) ) { ?>
<span></span>
<?php
}

echo '</a>';
echo '<ul>';

if ( $notifications ) {
$counter = 0;
for ( $i = 0; $i < count($notifications); $i++ ) {
$alt = ( 0 == $counter % 2 ) ? ' class="alt"' : ''; ?>

<li></li>

<?php $counter++;
}
} else { ?>

<li><a href=&quot;loggedin_user->domain ?>"></a></li>

<?php
}

echo '</ul>';
echo '</li>';
?>

And as I have found out, the js effect (what you called the “mouse over” effect) is dealt automatically by bp-themes/bp-default/_inc/global.js

In my case, I’m building a child theme of bp-default, so I don’t have to worry about js, just copy and paste css codes from bp-themes/bp-default/_inc/css/adminbar.css and adjust selectors accordingly.

If you are not building a child theme of bp-default, then maybe you can try search in the global.js and make some copy and past.

Good luck !

Add the following to your theme’s functions.php:

`function ray_bp_remove_settings() {
global $bp;

// removing the existing settings tab
bp_core_remove_nav_item( $bp->settings->slug );
}
add_action( ‘init’, ‘ray_bp_remove_settings’, 0 );

function ray_bp_readd_settings() {
global $bp;

// add a new settings tab to use notifications as default tab
bp_core_new_nav_item( array( ‘name’ => __(‘Settings’, ‘buddypress’), ‘slug’ => $bp->settings->slug, ‘position’ => 100, ‘show_for_displayed_user’ => false, ‘screen_function’ => ‘bp_core_screen_notification_settings’, ‘default_subnav_slug’ => ‘notifications’ ) );

// bug in bp_core_remove_subnav_item(), we have to hack the screen function so it displays the notifications screen when you land on /settings/
if ( $bp->current_component == $bp->settings->slug && $bp->current_action == ‘general’ )
add_action( ‘wp’, ‘bp_core_screen_notification_settings’, 3 );

// add back the subnav notifications tab
$settings_link = $bp->loggedin_user->domain . $bp->settings->slug . ‘/’;

bp_core_new_subnav_item( array( ‘name’ => __( ‘Notifications’, ‘buddypress’ ), ‘slug’ => ‘notifications’, ‘parent_url’ => $settings_link, ‘parent_slug’ => $bp->settings->slug, ‘screen_function’ => ‘bp_core_screen_notification_settings’, ‘position’ => 20, ‘user_has_access’ => bp_is_my_profile() ) );
}
add_action( ‘init’, ‘ray_bp_readd_settings’ );`

Tested lightly. Encountered a few bugs, but this will work…

Fixed in the 1.2 branch – courtesy Andy:

https://trac.buddypress.org/changeset/2921

[EDIT]

For friend requests… haven’t encountered the other issues above yet.

I’ve run in to this with importing a userbase to a Buddypress install. WordPress likes login names to be lowercase, with no spaces, and no non-alphanumerics (except, I think for dashes (‘-‘).

Users can, of course, make their display name anything they like.

The follow-on problem though, is with @username notifications in BP1.2+, which work on the login name and not the display name, so if a user has the login username johnsmith and the display name John, only @johnsmith will work.

(I’ve also just recently encountered a problem in that usernames with dashes cause @notifications to fail. That is, if a username is johnsmith, @johnsmith works, but if his username is john-smith @john-smith fails.)

@LwEEs

You can also place this code anywhere you want and style your own little Notifications Block:

<!-- Notifications block -->

<?php

echo '<li id="notifications-menu"><span id="menu-title">

<a href="' . $bp->loggedin_user->domain . '">';

_e( 'Notifications', 'buddypress' );



if ( $notifications = bp_core_get_notifications_for_user( $bp->loggedin_user->id ) ) { ?>

<span><?php echo '('.count($notifications).')' ?></span>

<?php

}

echo '</a></span>';

echo '<ul>';



if ( $notifications ) { ?>

<?php $counter = 0; ?>

<?php for ( $i = 0; $i < count($notifications); $i++ ) { ?>

<?php $alt = ( 0 == $counter % 2 ) ? ' class="alt"' : ''; ?>

<li<?php echo $alt ?>><?php echo $notifications[$i] ?></li>

<?php $counter++; ?>

<?php } ?>

<?php } else { ?>

<li><a href="<?php echo $bp->loggedin_user->domain ?>">

<?php _e( 'No new notifications.', 'buddypress' ); ?></a></li>

<?php

}

echo '</ul>';

echo '</li>';

?>

Thanks. That clears things up. The only other problem I’ve encountered is after I deactivate the BuddyPress plugin and re-activate it, I’ll get the follow db errors:

WordPress database error: [Duplicate key name ‘useritem’]

ALTER TABLE wp_bp_notifications ADD KEY useritem (user_id, is_new)

WordPress database error: [Table ‘wp_bp_activity’ already exists]

RENAME TABLE wp_bp_activity_user_activity_cached TO wp_bp_activity

WordPress database error: [Duplicate entry ‘1’ for key 1]

INSERT INTO wp_bp_xprofile_groups VALUES ( 1, ‘Base’, ”, 0 );

WordPress database error: [Duplicate entry ‘1’ for key 1]

INSERT INTO wp_bp_xprofile_fields ( id, group_id, parent_id, type, name, is_required, can_delete ) VALUES ( 1, 1, 0, ‘textbox’, ‘Name’, 1, 0 );

Just experienced the OP’s problem.

I looked into it and found a tentative fix… though a BP dev will need to look at the code.

In “bp-core/bp-core-notifications.php”, look for the bp_core_notifications_for_user() function.

Then look for these lines:

$item_id = ( 1 == $action_item_count ) ? $component_action_items[0]->item_id : false;

$secondary_item_id = ( 1 == $action_item_count ) ? $component_action_items[0]->secondary_item_id : false;

Change this to:

$item_id = $component_action_items[0]->item_id;

$secondary_item_id = $component_action_items[0]->secondary_item_id;

I don’t know why there was a check done for only 1 item and then returning false for more than 1… if a BP dev can explain why, that’d be great.

Let me know if anyone encounters any problems.

Trac ticket made.

@gpo1

Due to all communication of buddypress and bbpress being done over xmlrpc, the normal plugins most likely won’t work. I have been looking at ones like a view counter and they require massive modification of buddypress. Because of caching, the forums are not always pulled from bbpress. So it would produce falsely low view count.

Also, group forums, are just a single forum in bbpress, this changes the administration and moderation of the forums and topics. If someone is a moderator on bbpress, they can moderate the whole site I believe, with buddypress a moderator is only a moderator of that group forum.

Hope this helps,

Brad