I see it’s a specific config… i doubt there’s a conflict. It’s just not ready for this kind of config.
it is now – Many, many thanks
though without the lovely css !!
span.sticky group
or
<span class = "sticky group">Sticky Group Name</span>
is absent in multi – network.
no false optimism – last active was the filter – no change i’m afraid
Think I got it done, perhaps not elegantly but seems ok
for multi-network —-> replace line 293 of bp-sticky-groups.php
with
$current_site = get_current_site();
$xid = $current_site->id;
$sticky_sql['from'] = $sql_args['from'] . ' wp_'.$xid.'_bp_groups_groupmeta gms,';
or more correctly replace line 293 of bp-sticky-groups.php ?
with
`$current_site = get_current_site();
$xid = $current_site->id;
if ($xid != “1”) {
$sticky_sql[‘from’] = $sql_args[‘from’] . ‘ wp_’.$xid.’_bp_groups_groupmeta gms,’;
} else if ($xid == “1”) {
$sticky_sql[‘from’] = $sql_args[‘from’] . ‘ wp_bp_groups_groupmeta gms,’;
}
assuming bp root on main blog is site id =1; if not substitute the correct site id.
most probably could be cleaned up.
Hi @valuser,
Thanks a lot for insisting on this one, as you made me found a silly mistake i’ve made !! I’m really ashamed of it.. wow !! I can’t believe i’ve made it.
Anyway, i’ve published 1.0.2 to correct this. To get a WordPress table name, hardcoding ‘wp_’.. is the very wrong way of doing it. We need to use $wpdb->prefix. In the particular case of BuddyPress group meta table, we need to use $bp->groups->table_name_groupmeta.
confirmed 1.02 imends this.
Many many thanks
the other issue is that it must be network activated.
it would be nice to only activate it on individual sites
