BuddyPress.org

Multi-network does have some issues (and has been real-world tested by relatively few people), so it could well be that this is a bug.

I’m a bit confused about how to reproduce, though. Is the issue

(a) that when you have activity streams from different networks on the same install open in the same window, and post to the stream in one of them,…[Read more]

@dennish The installation of bbPress that is packaged with BuddyPress contains a file at buddypress/bp-forums/bb-config.php. When you attempt to access the bbPress installation directly as you describe, the bbPress bootstrap loads this bb-config.php file, and sends a 403 Forbidden header to the browser. Thus, it should NOT be the case that users…[Read more]

– Yes, 'nav_item_name' should be translatable if you plan to distribute the plugin. If it’s for a custom installation, it doesn’t matter.

– Yes, you can set 'enable_nav_item' (or any other config value) conditionally. I’d do your conditional logic *inside* of the constructor, to be sure that it’s loaded late enough:
function __construct() {…[Read more]

The problem is, in essence, this: You are filtering for member type/role at the template level, *after* the query has already taken place. So: you run bp_has_members(). It returns 10 users that match the current params, which include the current page, the per_page number, and the dropdown filter (last active, alphabetical, etc). Then, inside of…[Read more]

It’s hard to tell exactly without knowing more about how you’ve customized your templates, but it’s possible that this is a problem only with AJAX. A quick fix may be to disable AJAX pagination for the members directory. Do so by adding the ‘no-ajax’ class to the .pagination div, ie

<div id="pag-top" class="pagination no-ajax">

If you’re still…[Read more]

You’ll have to do some more debugging. It’s probably the case that $test_customfield is empty; try var_dump( $test_customfield ); just after you’ve defined the variable, just to be sure. It’s also possible that the $post global does not contain the information that you want at this particular point in the WP load order. Try passing the $post…[Read more]

Try this:
function test1() {
return 'this not';
}