[Jonathan]

If you’re brave, you could also try my fork of buddypress-docs. It fixes quite a few bugs (see the closed issues for a list), among which are a number of permissions-related issues. It also gives you a new theme which allows you to strip down some of the features which might be seen as unnecessary, like setting parent docs. However, it hasn’t been tested on many systems, so use with caution.

[Jonathan]

@iurie, It should be fixed now. Give it a try, and let me know how it looks on your system.

[Jonathan]

@Ray, thanks! That solved the issue. It was just missing this header.

[Jonathan]

@iurie, I’m looking into that at the moment. That happens to us, too, if we change themes then change back to cbox-mla! Which is quite worrying. I just opened a thread about it here:

https://commonsinabox.org/groups/help-support/forum/topic/reloading-child-theme-causes-errors-with-loading-infinity-functions/

I have a feeling it’s because the theme genealogy (cbox-mla -> cbox-theme -> infinity) is getting mixed up somehow, but I’m not yet sure how. If you have any ideas, let me know.

[Jonathan]

Does this comment refer to a feature that no longer exists in CBOX?

[Jonathan]

I just submitted cbox-theme issue #205 for this, and submitted a pull request that fixes it. I thought of submitting a pull request to BuddyPress for this (which would fix this issue directly in the function bp_profile_group_tabs, rather than just filtering the output), but since there also needed to be a check in the theme template to handle empty profile group tab uls, it seemed more logical to make this a CBOX change, rather than a Buddypress one. I hope other people find this useful! (And by useful I mean not useful at all, just cleaner and nicer.)

• This reply was modified 10 years, 6 months ago by Jonathan. Reason: fixed links. Why u no markdown!?!

[Jonathan]

@haystack Out of curiosity, how are you enqueuing your own stylesheets? That may indeed be easier than debugging from dynamic.css, which for me involves a ridiculous amount of grepping.

[Jonathan]

Your code didn’t seem to disable forums on child sites in my install at least. Maybe something somewhere wasn’t taking. I didn’t see any relevant error messages in the debug.log, and I didn’t get the fatal error about the undefined function, so it’s a mystery to me.

But I really like if ( is_multisite() AND ! is_main_site() ) { so I went with that in my final version.

[Jonathan]

Thanks, Christian. I wasn’t able to get that code to work, but I did finally get it to work with this, however:

function mla_remove_forums_from_child_sites($plugins) {
    global $current_blog;
    if( $current_blog->blog_id != 1 ) {
      unset($plugins['bbpress/bbpress.php']);
    }
    return $plugins;
}
add_filter('site_option_active_sitewide_plugins', 'mla_remove_forums_from_child_sites');

I’m sure this is probably not the most best-practices solution, but I hope it’ll work as a stopgap measure until there’s better plugin activation scope ability in CBOX. If you have any suggestions for how to improve this, definitely let me know.

• This reply was modified 10 years, 8 months ago by Jonathan.

[Jonathan]

Thanks very much for all the input. Using define( 'CBOX_OVERRIDE_PLUGINS', true );, I’m able to disable bbpress on the network and enable it on the root buddypress blog, but that unfortunately causes the issue where users lose capabilities. Instead, it looks like I’ll need to keep bbpress enabled network-wide, yet disable it for all child sites except for the root site. Do you know if there’s a way to do that, say, by hooking into CBOX’s plugin management in some way?

[Author]

Posts