BuddyPress.org

First off, I visited your site and confirmed that BP Album+ is working correctly.

You’re having problems because you’ve modified wordpress to display one URL in the browser while running the actual site on another …this is VERY BAD, because the modification you’ve made only handles *one* of *many* ways plugins generate URLs and file paths. That’s why we had to modify part of the BP Album+ code for you so it would work on your site.

Modifying BP Album+’s activity stream code to work on your site would be much more difficult. The code gets the base URL from BuddyPress; so we would have to hook the BuddyPress function that does that and modify the URL, and that could break other parts of your installation. It would require testing and debugging, and so on.

Also, version 0.1.9 of BP Album+ (which I’m taking a break from coding to answer your post) has at least *fifty* different functions that would have to be modified so it would work on your site, which is completely impractical to do.

Fortunately, you can fix *all* of these problems quickly and easily, have WordPress in a subdirectory, and have the subdirectory invisible in the URL, by properly setting up your web server.

Here’s how:

http://httpd.apache.org/docs/2.0/vhosts/

^F^

is_user_logged_in() is present in both WP and WPMU. Odd. What versions of WordPress/WordPress MU are you using?

You can always install bp later when you have your site up and running, so you can do both. But imo its better to use buddypress from the start because it soul purpose is to built a community with and its a great way to let your members and blog owners interact.. So I include it from the start

For those interested, the plugin etiviti (rich!) created for this issue can be found here:

BuddyPress Restrict Group Creation

https://wordpress.org/extend/plugins/buddypress-restrict-group-creation/

Sounds like a plan.. It’s a matter of weeks until WP 3.0 is out, and BuddyPress will be compatible from day 1, so you might want to launch the site when WP 3.0 is out with BuddyPress from the start! Good luck!

to answer both of your final questions: Yes and Yes!

@akingston47: What you’re looking for is basic WP functionality. If you want to see all of the posts for a category, navigate to the category index page/URL like @Jamesmarsland suggested.

If you want to do this on a page, you need to modify WP “the-loop”. There’s a whack of information on the WP codex about how to do this sort of stuff.

https://codex.wordpress.org/The_Loop

The only difference is that if you use MU then your users can create blogs.

Folks,

The issue here with 3.0 is that if an existing WP 2.9.2 install with uploaded media upgrades to 3.0 and enables the network the blog option for the upload_path can’t be changed to the blogs.dir folder because the existing media becomes inaccessible.

For now, if you are looking to go to multiple blogs after install, then you should install MU 2.9.2 and upgrade that to 3.0 instead of installing WP 2..9.2.

@heini-

Your basic idea is correct. The issue is the order in which each action function hooked to the bp_setup_nav action event is being triggered. Let’s look at the code you have in bp-custom.php.

<php

function my_groups_setup_nav() {

[the whole function code]

}

remove_action('bp_setup_nav', 'groups_setup_nav');

add_action( 'bp_setup_nav', 'my_groups_setup_nav' );

?>

This fails because your custom code in bp-custom.php is executed before the code in bp-groups.php is executed. So, you are calling to remove an action that has not yet be registered by WordPress.

I’m almost finished with an article about the intricacies of WordPress’ action and filter functions, but here is a brief explanation to try to shed some light on the issue.

Each action and filter event when triggered by a do_action or apply_filters call sends execution to the appropriate do_action or apply_filters function in /wp-includes/plugin.php. These functions do several things, one of which is querying a very large array that contains all of the added filter functions and action functions. This array gets populated by the actions of the add_filter and add_action calls.

To avoid getting too long winded, as each file gets loaded, any and all add_action and add_filter calls that are directly executable at the time, get triggered which builds this big array. This array is then used by the do_action and apply_filters functions to determine the sequence in which each added action of filter will be executed.

You can read my article when it is ready for a much longer but clearer explanation.

With that briefly described, the piece of information that applies to your situation is that when the action event for bp_setup_nav is triggered, via the do_action( ‘bp_setup_nav’ ) call on line 2025 in bp-core.php, the do_action function starts processing each action function that was “added” to it in the order in which it was added (with an important exception). This means that for your custom function my_groups_setup_nav to work, it must remove the action function in the array discussed above so that when the bp_setup_nav action event is triggered it uses your action function instead of the one added by the add_action(‘bp_setup_nav’, ‘groups_setup_nav’) call.

So, what you need to do is trigger your remove and add action calls in the proper sequence–after the action function that creates the groups navigation menus has been added to the filter array but before the bp_setup_nav action event is triggered. I realize this may be hard to understand.

This is what you need to do instead:

<?php function my_groups_setup_nav() {



/* Remove the added action from the array of functions that get run

* when the action event for bp_setup_nav is triggered

*/

remove_action('bp_setup_nav', 'groups_setup_nav');



// Then replace the removed function with your custom content

[the whole function code]



}

add_action( 'plugins_loaded', 'my_groups_setup_nav' );

?>

A final bit of clarification. This is what happens in your current custom function:

1. As soon as BuddyPress is initialized, it looks to see if bp-custom.php exists. If it does, it loads it.

2. This will cause your remove_action call to be fired.

3. But the corresponding action has not yet been added to the very large filter array since bp-groups.php has not yet been loaded.

4. So, nothing happens as there is nothing to remove.

5. bp-groups.php eventually gets loaded and at that point the add_action(‘bp_setup_nav’, ‘groups_setup_nav’) call is fired, resulting in the action function that you were trying to remove getting added to the filter array but after the fact.

6. Eventually the bp_setup_nav action event is triggered.

7. When that happens, the first function hooked to it (added to it) is your custom function. It now gets triggered.

8. All other action functions hooked to the bp_setup_nav action event get triggered one by one including the groups_setup_nav function–the one you had tried to remove in step 2.

9. You have a mess with two duplicate functions doing the same thing.

BuddyPress is still young and so it doesn’t have the same kind of rich development guides as the much more mature (and widely-used) WordPress.

Since BP is a WP plugin, the basics of BP plugin development are the same as they are for WP. The system of hooks and filters is exactly the same (though of course the hooks themselves are different).

At this point in the BP project, I’ve found that the best ways to get started with plugin development are (a) to find existing BP plugins that do something similar to what you’re trying to do, and to learn by dissecting them; (b) to look through official resources like the ones Jeff posted above; and (c) to search through BP codebase itself, where I think you’ll find that many of the functions you need are quite well documented.

I am running it off a sub-folder in WP 3.0. I have been for a long time but the most recent upgrade broke my avatars. It looks as if the image uploads correctly for me, but doesn’t pull it in to crop. The path it try’s is:

http://www.website.com/sub-folder-blog/blogs.dir/2/files/avatars/1/avatar.jpg

when it should be

http://www.website.com/wp-content/blogs.dir/2/files/avatars/1/avatar.jpg

Any ideas on what I should try to change? I’ve already tried:

Thanks!

I had the same problem a few seconds ago. A newly registered member didn’t recieved the activation email but was listed in WordPress>Backend>Users

I asked the user to check spam inbox twice but there was stil no activation mail

It would be great if admins could manually acivate such users or resent the activation email.