BuddyPress.org

I don’t think it’s unfair that we revise the theme and any of the bundled widgets with each release. We need to be able to iterate on all areas of the theme (and other presentational elements) in order to continue to improve and add new features to BuddyPress. As Rich says, to remove the secondary avatar, put this into your functions.php:


remove_filter( 'bp_get_activity_action_pre_meta', 'bp_dtheme_activity_secondary_avatars', 10, 2 );


@djpaul

OK, apology in order – my temperature sizzled, and I jumped to the conclusion that they were being added in the core, and not as a filter in the default theme (which is a damn good place for them!).

Now, if only you could tear half the other activity presentation stuff out of the core – or leastways create some more granular template tags / functions – so that we’re not stuck PHP unlocking those monolithic activity strings. That would be really lovely.

Apologies again, bit of humble pie for me, and @nuprn1 .. thanks for pointing out the filter

Better that individuals don’t just pile in to trac adding enhancement tickets wily nily for this sort of area. We need a task group set up to tackle this that looks at what is required, and draws up a list of things to tackle, template tags that are needed etc.

I really like that we’re now showing the group avatars in the activity stream updates. But I’ve noticed a “bug” in the Recent Site Wide Posts widget.

As you can see the blogs are just showing random avatars and aren’t showing the users’ avatars like 1.2.5 used to. Any ideas?

Here’s another discrepancy in the activity stream:

This change is not documented nor annouced in the update post on the BP blog.

About this “some minor tweaks to the included theme”, nobody knows what to do,exactly to retrieve or edit this gravatar. Except here in this tread, which will be buried in the next 3 days in the deepness of this forum
I consider this a bit unfair to find such a picture at this strategic place represented by the SWA page without any permission ! This change can also (as already mentionned) compromise some fine tuned template skills. And what to say about breaking long discuted graphical convention ?
I want at minimum have the possibility to change it, like i can do it for my group avatar for ex.

In 2009, we could choose to use wavarar, gravatar or monsterID from within the admin.
Since 1.2.2 or so, Gravatar is gone (silently) from the admin interface. Now he’s back via SWA….

What do we do(and think) tomorrow, if suddenly Gravatar.com send us an advertising icon instead of a graphic abstract as actually ?
What the sense of all those thousands of millions of icons flying around the web ?
Only to have pretty links or to organize some juicy statistics and server consumption ? The non GPL part of the trick i guess….

The whole point of having a child theme is inheriting all the cool, new features of the parent theme; I think we shouldn’t be making comments after the fact BP 1.2.6 was released. The core team asked many times for testers to the 1.2 branch; some did test, but many did not.

Like it’s been stated, secondary avatars can be removed by getting rid of the filter. I do agree that blog avatars shouldn’t be used since you can’t even declare a blog avatar yet. However, you can get rid of that quite easily by duplicating the secondary avatar function and removing the “blogs” case.

The following code will work in your theme’s functions.php:

`function ray_secondary_avatar_fix() {
remove_filter( ‘bp_get_activity_action_pre_meta’, ‘bp_dtheme_activity_secondary_avatars’, 10, 2 );

// add the following if you still want secondary avatars, but omitting the blog one
function my_bp_dtheme_activity_secondary_avatars( $action, $activity ) {
switch ( $activity->component ) {
case ‘groups’ :
case ‘friends’ :
// Only insert avatar if one exists
if ( $secondary_avatar = bp_get_activity_secondary_avatar() ) {
$reverse_content = strrev( $action );
$position = strpos( $reverse_content, ‘a<' );
$action = substr_replace( $action, $secondary_avatar, -$position – 2, 0 );
}
break;
}

return $action;
}
add_filter( ‘bp_get_activity_action_pre_meta’, ‘my_bp_dtheme_activity_secondary_avatars’, 10, 2 );
}
add_action( ‘init’, ‘ray_secondary_avatar_fix’, 9 );`

I do agree that there should be a better changelog for changes made to bp-default. Maybe in the codex?
[ EDIT: changelog created here – https://codex.buddypress.org/extending-buddypress/bp-default-theme-changelog/ ]

Wordpress will most likely build on top of 2010. They will not make a theme called 2011, unless the design is radically different.
Much like Kubrick to 2010 was a totally different design.

For example, P2 adds features on top of their theme all the time and I think a lot of people appreciate that.

Maybe new features should be a theme option…

@r-a-y :

p.s. I do agree with you on a number of things here –

yes: new features as theme options (opt-ins, not outs), and yes: it’s probably part of a wider jigsaw – a well developed Codex would have helped, as would a much clearer / better signposted buddypress.org (invitations to test 1.2. and how to, were only obvious to a knowledgable few – which may explain the small uptake).

@gwu123 – code snippet has been revised; forgot to set priority so it runs earlier.