BuddyPress.org

BuddyPress has no deactivation script so you don’t accidentally delete your content

As the header on that page says that component has been depreciated any theme should be basically compatible with buddypress “out of the box” more info can be found here:

Theme Compatibility & Template Files

Same problem here, when any of my users go to their Notifications page it is blank. I’m on latest BuddyPress release with BuddyBoss theme with no customizations.

Use this hook: do_action( ‘bp_activity_entry_content’ );

in the template: buddypress\bp-templates\bp-legacy\buddypress\activity\entry.php

And write a function to embed the video.

Ciao! The current version of BuddyPress only has 3 tabs when you click on the group:
Visit|Edit|Delete.
No Admin.
Anywhere else I can look.

Another idea. My understanding is that this can be done through child-themes, but seems kind of taxing for what I would think should be a standard feature.

There should be a means to configure the Activity Stream in the Buddypress settings. I don’t necessarily think that all my users should see everytime someone becomes a friend with someone else. This would be a bonus IMO.

I have run into an issue where I converted a vBulletin forum over to bbpress/buddypress combination.

I really do not quite understand why, but over the course of the past week since the migration. Me and my users have been getting non-stop emails 50-100 a day with @mentions. The longer a user has been involved in the community, the worse it got. I started out by completely disabling emails from WordPress, then I found r-a-y’s no mention plug-in. I’m hoping that does the trick.

Either way, there should be a way to disable certain notifications or messages transmitted from Buddypress.

Kudos to all the devs that work on this project! Thank you.

you should be okie to reupload the buddypress directory into wp-content/plugins without reinstalling but if it will make you feel better having a flawless installation for peace of mind go right ahead.

it did sound like an .htaccess problem.

@houndlounge great to see you managed to find a solution but, just be aware with that particular solution, if you upgrade BuddyPress your changes will be lost

Now fixed in trunk for BP 2.0. Thanks for the report and the fix, @glyndavidson

https://buddypress.trac.wordpress.org/changeset/7740

Hi @megainfo. I really appreciate all the work you’ve put into this much needed plugin! I found one easily rectifiable problem with the snippet of code in the bp_visibility_activity_filter() function you added for the re-inclusion of @mentions.

        // mentioned members can always see the acitivity whatever the privacy level
        if ( $visibility != 'mentionedonly' ){
            $usernames = bp_activity_find_mentions( $activity->content );
            $is_mentioned = array_key_exists( $bp_loggedin_user_id,  (array)$usernames );

            if( $is_mentioned )
                $remove_from_stream = false;
        }

When there are no @mentions in the content and $usernames returns blank, you cast $usernames as an array in order to keep array_key_exists from complaining. An unfortunate side effect of this turns out to be that (array)$usernames is an array with a single key-value pair of [0] -> ” and $bp_loggedin_user_id is 0 for a non-logged in user, thereby allowing a non-logged in user to see things they shouldn’t.

It took me a little while to figure all of this out, so please accept my patch as thanks for all your hard work!! I’ve modified my version of your code to the following:

        // mentioned members can always see the acitivity whatever the privacy level
        if ( $visibility != 'mentionedonly' && $remove_from_stream ){
			$is_mentioned = false;
            $usernames = bp_activity_find_mentions( $activity->content );
			if ( is_array($usernames) )
				$is_mentioned = array_key_exists( $bp_loggedin_user_id, $usernames );

            if( $is_mentioned )
                $remove_from_stream = false;
        }

I also added the && $remove_from_stream to the if statement, because there is no reason to run the additional code if the activity can already be seen.

I wonder if this is the reason @burakbirer says that Buddypress Activity Privacy 1.2.1 doesn’t work with BuddyPress 1.9.1? Everything else seems to work fine for me in that environment.

Many thanks,
Scott

Hi @jayjaym,

Remove “buddypress” tag from wp-content/themes/platfrom/style.css

Tags: buddypress, rtl-language-support, editor-style, theme-options, one-column, two-columns, three-columns, left-sidebar, right-sidebar, flexible-width, custom-menu, fixed-width, threaded-comments, custom-background, custom-header, custom-colors, custom-menu, photoblogging, translation-ready, white, silver, light, blue, green, yellow

let us now if it’s work !

Yep, likewise. Not sure when we’re going to close the survey — maybe the end of the month, but we should have some preliminary data available to help plan BuddyPress 2.0 at next week’s dev chat.

https://buddypress.trac.wordpress.org/ticket/5344#ticket

Please report this as a bug on buddypress.trac.wordpress.org. Thanks.

Bug reports for BuddyPress.org itself should also be reported on buddypress.trac.wordpress.org, please.

1 – edit your style.css of your theme, and remove buddypress from tags :

Tags: buddypress,white,one-column,two-columns,three-columns,right-sidebar,fixed-width,editor-style,custom-menu,custom-header,featured-images,full-width-template,theme-options,threaded-comments

2 – remove all this directories if they exisit on your theme :
‘activity’, ‘members’, ‘groups’, ‘bbpress’,’blogs’, ‘forums’, , ‘_inc’, ‘registration’.
(mybe you will find these directories on others sub dir like ‘lib’ or ‘buddypress’.

Hope this can help you!

BP experts seem to know (or are willing to share) the answer

Firstly it isn’t really something that requires BP expertise nor is it some secret people are trying to hide from you.

CSS is coding and requires some degree of understanding if you wish to start modifying code to some degree you’ll have to leave behind that notion of being a non expert 🙂

There is no general bit of code that can be provided to suit all users in this request, the start point for stating a general font color is the body tag as this is a inherited property however then that color can be overridden with other values further on down into the cascade so if it didn’t work on the body tag likely it is being stated somewhere else and as there is no particular set notion as to where as this is a stylesheet authors decision it’s hard to give anything other generic approaches. Using a tool such as firebug in FireFox you may be able to examine the elements that have styled text and see where they inherit things like color properties from in the stylesheet and then adjust accordingly.

@henrywright approach adding !important might work however it’s not a good practise (sorry Henry 🙂 )

The reason people are always advised to use child themes is that this way you can make changes and be assured they won’t get overwritten in updates, now in your case looking at your custom theme with very bold coloured backgrounds the rules in the buddypress.css stylesheet that set activity meta to grey would need changing but to do this you would want to copy over that stylesheet or in your themes styles write very specific rulesets to override the BP ones.

The process for copying over BP files is described here:

Theme Compatibility & Template Files

I think you’ll be fighting an uphill battle trying to do this with PHP in the editor. When you add PHP into a regular page, the page doesn’t realize it’s supposed to be running BuddyPress code and you may be missing some critical opening/closing PHP outside of the core messages code. You’ll probably need to set up an actual page template just for this and then set your WP page to use that template.