[Ash Shaw]

Thanks guys. Roger, that’s exactly what I was looking for, and works a charm.

[Ash Shaw]

Thanks for replies

[Ash Shaw]

Can anyone confirm whether the above is standard BuddyPress behaviour? Is editing posts meant to bump them to the top of the activity stream?

[Ash Shaw]

Just worked out that this only applies to updates that were posted before changing ‘members’ to ‘participants’. So all new updates do link properly to the correct profile pages, but the older updates still link to the old urls, which no longer exist. This shouldn’t be a problem going forwards.

[Ash Shaw]

I see what you mean – I tried the following function:

`function limit_blog_activity() {
global $wpdb;

if ( $wpdb->blogid != BP_ROOT_BLOG ) {
remove_action( ‘save_post’, ‘bp_blogs_record_post’, 10, 2 );
}
}
add_action( ‘save_post’, ‘limit_blog_activity’, 5 );`

This doesn’t have any effect, since the site where the post is saved will always equal BP_ROOT_BLOG.

Would it not be a better idea to limit the activity loop to only display activity from the current site? I’ve taken a quick look at the bp_has_activities function and it looks like this might be achievable through ‘primary_id’ and ‘secondary_id’ parameters, but am not entirely sure how I would apply this.

Or do you have any other suggestions to limit updates, posts and comments to current site dynamically?

Thanks.

[Ash Shaw]

Thanks a lot. In our case each site on the network will be using buddypress, but they won’t be sharing posts / comments between them. Also, all of these sites are sharing a single child theme. I suppose I could add a condition to the function to whitelist only the current site id, preventing updates streaming in from any of the other sites. Will give it a shot.

[Ash Shaw]

Thanks Boone. Actually, having deactivated and activated the plugin for the umpteenth time, we’re now getting the options per site (literally minutes after my forum post, as it goes ).

Will definitely look into the BP multi-network plugin, looks like we might need it. It’s my understanding that the only way to have new posts and comments show up in the activity stream is by activating the site tracking component. However, surely this means that all posts and comments from across the network will appear in the stream. Is it not possible to only feature posts / comments from the current site, or is this where the multi-network plugin comes in?

Appreciate the help.

[Ash Shaw]

I started a new topic for the latest query here – https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/bp-1-5b2-bp-options-per-site/

[Ash Shaw]

Thanks for clarifying. I thought that enabling site tracking would update the stream with posts/comments from all sites in the network, whereas disabling would only feature those on the current site. Have now been able to establish that posts/comments aren’t showing up because the dev site is private and not index-able.

– Is it possible to only feature posts/comments from the current site, even with multiple sites on the network? – Also, how would we go about enabling the bp options per site?- We’re working on a network of sites in different languages, and thus need the ability to define specific slugs/titles for bp components per site.

Appreciate the help.

[Ash Shaw]

I’ve updated to the latest build of the beta, but posts and comments are still not showing up in the stream.

On my local site, if I enable the ‘Site Tracking’ component, new posts and comments show up correctly in the stream as “x wrote a new post, y , on the site z”. If I disable Site Tracking then no posts or comments show up in the stream at all.

On the dev site, no posts or comments show up in the stream regardless of active components. Also, locally the BP options show up on my site admin page (plugin is network activated), but on dev they appear on the network admin page – not sure if this is related. (We will need the bp options to show up on each site in the long run, but I’ll save that for another thread)

Thanks.

[Ash Shaw]

Just a correction on WP version: should be 3.2.1

[Ash Shaw]

Cool, thx for the quick reply

[Ash Shaw]

Thanks for the response DoctorDR. I’ll keep hacking away at getting woo-pagenav to work, at least I know now that it can be done

Here’s the loop we used to call all public images to the gallery page.

`<?php
global $bp, $pictures_template;
$args = bp_album_default_query_args();
$args = ‘DESC’;
$args=24;
bp_album_query_pictures($args);
?>

<?php
$user_ided = $pictures_template->picture->owner_id;
$user_link = get_userdata($user_ided);?>

<a href="user_login. ‘/album/’; ?>” class=”picture-thumb”><img src='’ />
<a href="user_login. ‘/album/’; ?>” class=”picture-title”>

`

[Ash Shaw]

Forgot to include url – http://connect123buzz.wwc.co.za/gallery/