BuddyPress.org

@chatty24, all readers,

the modified code used here throws a warning with BP 2.2. Don’t use it !

FYI the title code after applying the snippet looks like this:
<title>You Have 1 New Notification(s) - </title>
You can probably remove the –

Thxs @sbrajesh, you where faster as me ! 😉

Hi Fan,
Do you mean removing the tabs in user profile ?
If yes, Please visit Dashboard->Settings->BuddyPress then click on the components tab.
there you can disable the Notifications and settings component.

If you are using WordPress multisite, you can find the BuddyPress settings under NetworkAdmin->Settings->BuddyPress

Hope that helps.

Hi Chaitanya,
Try this code.

function bpfr_add_notification_to_page_title( $title, $original_title, $sep  ) {
	
	//do not change if the user is not logged in
	if( ! is_user_logged_in() )
		return $title;
	
	$user_id = get_current_user_id();//logged in user's id
	
	$count = bp_notifications_get_unread_notification_count( $user_id );
	
	if( $count > 0 )
		$title = sprintf( "You Have %d New Notification(s) - ", $count );
	
	return $title;
	
	
}
add_filter( 'wp_title', 'bpfr_add_notification_to_page_title', 100, 3 );

I have modified the code from your last post. The difference is, It only does it for logged in users. Also, I have decreased the priority to make it work on BuddyPress pages( otherwide bp_modify_title would have overwritten it).

Hope that helps.

@henrywright is right. There is only one js file handling whats-new: buddypress.js and one function: bp_activity_action_post_update() in bp-activity-actions.php:289 (2.2) and of course CSS, in buddypress.css

Thought you have to use the minified versions to get customization to work.
buddypress.min.js
buddypress.min.css

There’s 2 types of notifications: a) read and b) unread.

bp_notifications_get_unread_notification_count( $user_id ) will get you the unread count so you could use that value in the comparison you mentioned here.

I think you’re right in that bp-legacy files are used when a file doesn’t exist in your templates folder. In this case though I’m not sure the same applies as it’s a .js file. Perhaps @danbp will know what happens in this instance?

Update: After a little research, it seems as though the same does apply to .js files. See here which loosely mentions .js files

* As of BP 1.8 the paths for assets i.e styles and JS has been modified to look to your ‘buddypress’ or ‘community’ folders first…

So you’re right to think the JavaScript that expands the what’s new textarea on focus may exist elsewhere. But unless you’ve explicitly created the file in your theme, then bp-templates/bp-legacy/js/buddypress.js should be the only place.

hi,

increasing the avaible memory means php memory, which handles scripts.
On a usual install, WP+BP need at least 128mo to run flawless.

Even if the server as the theoric resources, weird scripts or bad coded theme or plugins can lead to severe issues…

Read here for some basics about blank sreen of death.
This is actually the only issue which is real ! You have to consult the log files to track down the responsible script who generate this error.

Please give also more details about your install (theme name or site url, used plugins, server type and php, mysql version number) if you need more and/or better help.

Hi,

before asking for a fix, there is a need to identify the problem. You’re using 2 third parties plugin which you think are creating issues… Maybe, maybe not.

First of, give your site URL so other can try to help you eventually.
Second, if you’re sure one, or both plugins are defect somehow, you can ask on thei r respective support.

To be clear in regards of issues, ensure always that your base install is working correctly.
Is WP ok ? yes/no
Is BuddyPress ok ? yes/no
Is your theme ok ? yes/no

If 3 “yes”, each time you activate a plugin and something goes wrong, you’ll be sure it’s the plugin, and not your install. In 95% of cases, the culprit is the added extension.

This is a debug logic you can follow to find or try to, for explanations. 😉

Hi @number_6

I believe this is it:

https://github.com/buddypress/BuddyPress/blob/master/src/bp-templates/bp-legacy/js/buddypress.js#L58

Love the last one @chubbycrow !

Would see a smoothed version on closed topic ! Which looks really awfull actually.
https://buddypress.org/support/page/20/

#stars&stripes or #StarSpangledBanner ?
We now have the stripes, where are the stars ? That’s the question… 🙂

I’m sorry too, but i can’t learn you to use BuddyPress and WordPress. I can only guide you. It’s a volonteer based forum, and understand that i can’t offer you a lot of my time.

You asked how to apply at least a background color to the buddy nav.

The CSS code i indicated should go in a file called style.css
This file exist in almost any theme. Open it and copy/paste the code, save and bam, you’re done.

For more explanation about child theme or any other custom work, you have to read WP & BP‘s codex or find some tutorials on the net.

Be also aware that you use a premium theme, which can be difficult for you to find assistance outside of the theme support.

It’s intended so by default.

Try this from child-theme style.css
#buddypress div#item-nav div#object-nav ul li{background-color: #ccc;}

hi,

use the img button, you can insert an url.

Do you use the buddypress menu in wp’s menu manager ?

Hi jwind I did you managed to find a solution as I have the exact same issue… When I turn on Buddypress group and I sm logged in the pagination on the front page stops working however if I disable permanent links pagination works…

Baffled

Remove both the background colors.
Change the text color to black.

In In bb-base/style-buddypress.css:

#bbpress-forums p.bbp-topic-meta .bbp-topic-started-in a {
	/* background-color: #be3631; */
}

In bb-base/style.css:

#bbpress-forums p.bbp-topic-meta .bbp-topic-started-in a {
	color: #000000;
	padding: 2px 5px;
	border-radius: 3px;
	font-size: 10px;
	font-weight: bold;
}

Also @skyrant, it’s possible this is just a bug in our implementation, and using WordPress’s add_menu_page() function, which requires a capability be passed into it that is consequently checked on the current site being accessed, and not the root site where the bp_moderate capability is likely to be assigned.

I’ve opened a ticket in our bug tracker to bring a bit more attention to this as a bigger issue, so if you end up creating any patches, go ahead and drop them there:

https://buddypress.trac.wordpress.org/ticket/6175

Hey @ubernaut. All thoughtful consideration is appreciated and encouraged, but your “doesn’t currently exist in buddypress” response was neither, considering @skyrant appeared to already frustrated by BuddyPress not performing to his expectations.

It was also inaccurate, as functions like bp_current_user_can() exist explicitly to enable developers to extend this functionality. If skyrant is unable to make it work, more open-ended questions about the approach will help us figure out what’s not working correctly, be it on his/her end or ours.

And this…

please let me know if you feel like my participation is no longer desired around here

This isn’t the case, and if it ever was to be, never let that stop you anyways. We are all trying to build cool things and improve the world through better open-source community software. It’s inclusive at it’s core. Only twice in eight years have we excluded anyone because of clearly malicious abuse of other members, and it still bothers me to have needed to do so.

<3

Hey @skyrant, project lead chiming in here. Apologies for @ubernaut’s response; it doesn’t come across as very helpful or inviting, nor does it point you in any directions as to where to start building this type of functionality, which is the type of helpful reply I would expect from our forums normally.

You’ll want to look into WordPress’s map_meta_cap filter, and more specifically, our bp_moderate capability checks.

In the old days, we used a bunch of is_super_admin() checks to only allow the type of access you desire to network administrators. This proved to be too powerful an assumption once BuddyPress started working on Single-Site installations, and so we ported (almost) everything to checking for bp_moderate instead.

You could create a new role and grant it the bp_moderate capability. In doing so, any user with that role will have the ability to moderate the entire BuddyPress community.

This also is a bit more powerful than we would like it to be, and in the future we hope to introduce dedicated roles and capabilities all through-out BuddyPress very similarly to the way we did with bbPress. It’s not in the immediate roadmap however, so if this is an area you’re interested in, and want to help us improve it, let’s keep a dialogue going here and see if anyone else chimes in.

Oh i came across this issue in the past when trying out different themes, i cannot remember which theme it was that caused this for me but i did manage to solve it somehow but it was so long ago i just cannot remember, but it was definitely caused with a theme i tried and not buddypress, in the end i decided not to use that theme, so i would suggest finding a different theme first as @mercime said and if its the cause change to a diff theme unless you paid for it of course then make the issue known to the developer for a fix.

I tried to get the register.php from the legacy folder and put it in my own theme folder but it didn’t help.

@alesas If you copied register.php from legacy, then you’d have to paste it into yourthemefolder/buddypress/members/register.php Is that what you did?

edit – codex articles which can help you https://codex.buddypress.org/themes/theme-compatibility-1-7/