BuddyPress.org

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.

@marcella1981

Most plugin compatibility issues are either JavaScript or some template conflict. For templates, inspect the code in /buddypress/bp-templates/bp-legacy/. Make sure you’re basically following that model if you are adding your own BP template files, because many plugins add template files to output their HTML and they are basing their HTML on the structure found at /bp-legacy/. Also keep in mind some older plugins use the structure from bp-default (with /_inc/ storing templates and assets) and these older plugins may break the layout in your theme. For JavaScript, some plugins rely on the JS that BuddyPress runs, so let it run.

My advice:

1. Don’t copy bp-default. It’s a very old theme and is being retired. Instead, model everything off of the bp-legacy files. They’re at /plugins/buddypress/bp-templates/bp-legacy/

When BuddyPress runs (1.7+) it is pulling in templates files and CSS and JS from this folder. You can replicate that folder structure to override any templates in there, like CSS, etc.

2. If you want to completely override the default CSS, you can remove the enqueuing of it entirely with this in your functions.php, so that you’re not loading your CSS in addition to BP default CSS.

wp_deregister_style( 'bp-child-css' );
wp_deregister_style( 'bp-parent-css' );

3. Sounds like a nice plan of attack. I wouldn’t recommend using a separate stylesheet for every single component, because you’re going to end up with a ton of stylesheets which will be bad for performance. But if it makes your life easier to code this way, you can always combine all of the styles at the end. Also I think you may find that a lot of stuff overlaps between components. Like all directories are basically the same CSS (Member directory, Groups directory, etc.), and member profiles and single groups are basically the same CSS. So it may get redundant to separate by component. I would separate by directory, single item (profile, group), and then get specific for different “inner” content types – like messages, activity, etc.

To remove that for logged out users, go to Settings > BuddyPress > Settings. Make sure “Show the Toolbar for logged out users” is set to “No”. Then you’ll need a link somewhere for people to login/register. You can use the login widget packaged with BuddyPress 1.9+

Would be awesome to at least have a nice iPhone ready theme available.

BuddyBoss is an iPhone / Android compatible theme for BuddyPress.

http://www.buddyboss.com/

Hi,

I’ve read your post over the past couple of days as I was having the same problem and trying to find a solution after being stuck for weeks without any solutions or replies.
I’ve finally found a solution that works for me and I hope it works for you.

Deactivate BP 1.9.1 and delete it from your WP-admin page(I am not sure if you will loose your registered users etc – I didn’t). Go to the following buddy press link
and download version 1.8.1. Install under your plugins section, activate and test to see if it works.

Hope I helped, cheers.

Found the fix here.
https://buddypress.org/support/topic/notifications-tab-appeared-in-profile/

BP Activity Privacy 1.2.1 does not work with the Buddypress latest version 1.9.1.
Will there be a fix soon?

Thank you for this great plugin. Hope it works.

@stoi2m1 I’m not entirely understanding what you mean. Is the issue reported in this Trac ticket similar to your problem?

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

You’ve almost got it! Yes, create a new page for registration and then go back to the BuddyPress page settings and assign the register page.