BuddyPress.org

It won’t work with WordPress only WordPress MU at the moment.

yes i think this is the same problem i’m having …. the member’s blogs not the main admin one … the member blogs they can’t use a widget that displays any blog posts on their front page …. the only widget availble is a list and i mean

list of recent posts
what happens to the other widgets that are on the admin’s options like site wide activity or more importantly blog posts?

would like them to at least have a wordpress type latest posts homepage as their homepage on a buddypress/wpmu member blog

Although WordPress / MU use its own WP authentication methods, I would state that LDAP will never be a plugin module for BuddyPress.

BuddyPress is a plugin for Social Networking – asking it to deal with authentication is like wanting your office document application to play mp3’s.

Authentication however – within WordPress / MU is pluggable and if there is a plugin out there that supports LDAP, then give it a go as BuddyPress will only check if you are logged in or out and has nothing to do with authentication.

http://www.ohiofreedom.com/wordpress

What album plugin for wordpress mu do you recommend for now?

Sorry to hijack this thread, but I’ve been wanting to change the groups URIs, and ok, so I know that groups is hardcoded in.

But I tinkered around with it and basically created a GROUP_SLUG and set that, in my case, to “projects”. Everything works fine (I had to change a few template things but otherwise it’s ok) except I have a teensy weensy problem with the catchuri function

So now all my pages are something like siteurl.com/members/username/projects/action

(siteurl.com/members/username/projects/, siteurl.com/members/username/projects/my-groups, siteurl.com/members/username/projects/group-finder. You get the idea)

And it works fine until I create a wordpress page called projects, then for some reason siteurl.com/members/username/projects rewrites to siteurl.com/projects, which in my case would be the wordpress page instead of the groups memberpage. I’ve tried taking a look at catchuri, and playing around with the is_page function, but even if I try to name the page something else, like say “projects main”, it still ends up trying to add the template into the page, which naturally fails and ends up with the 404 template.

I also don’t know if it’s related, but my wordpress mu is in a subdirectory, which looking at the catchuri code, doesnt seem to deal with subdirectories at the first explosion of the uri to rewrite (but I may be mistaken), so before the explosion of the actual site_uri function, $bp_uri[component_index] ($bp_uri[0]) actually returns me the subdirectory that my wp mu is in. I’m not sure if this is a bug and/or if it affects muy uri rewriting, but I thought I’d mention it.

p.s. when I delete the projects page, members/username/projects rightfully shows me the my-group template.

you can take a look at it here http://donicethings.org/beta

If anyone could help me I’d be most grateful, thanks!

I’m with you ‘ricwes’! I can’t wait to implement BuddyPress into my website!!! This is really exciting. I can’t wait to see how it develops.

I’m preparing a proposal for my company to use WordPress for blogging too.

I think I’ve fixed it.

When using the BuddyPress function bp_core_do_catch_uri() via the ‘template_redirect’ action, there needs to be a remove_action() on redirect_canonical() to stop the BuddyPress redirection and WordPress redirection conflicting.

Basically adding a remove action on line 158 of bp-core-catchuri.php seems to work:

remove_action( ‘template_redirect’, ‘redirect_canonical’ );

add_action( ‘template_redirect’, ‘bp_core_do_catch_uri’ );

This seems to fix the problem of conflicting page names/group names.

BuddyPress is doing its own thing.

Take a look at bp-core/bp-catch-uri.php

The URL is split up into variables and used within plugins. This is obviously interfering with some of the WordPress URL’s. I’m going to take a look at this and see if there is a solution to put pages on a exclude list.

OK, I have submitted a better patch to allow complete customisation of the admin bar using add_action() WordPress hooks.

It also has log in and register and is available from https://trac.buddypress.org/ticket/174

Please Note, this patch will possibly not work if used on top of the previous patch, so make sure you have the original core files installed first.

Is there something specific you’re looking for. Most WordPress plugins and WPMU plugins will work alongside BuddyPress. Right now the focus is on getting all the basic features stable for a formal release in the next month or so, but additional plugins will definitely be developed for this system.

Yeah this works, I’ve done it on a recent install of BP where I didn’t want the WordPress admin interface being used. When the ability to update your blog from the main frontend comes along, I’ll re-enable.

Jordan

Andy,

I think I figured out what was causing the problem. When I originally installed WordPress MU, I had had to re-install it a few time until I got it right. File permissions weren’t set properly at the time of installation, etc. When I went into my “Sites” are of the Admin Settings panel, I found that I had about a half dozen sites listed, all with the same name. I deleted all except for the most current installation and now I am able to upload the avitar images. This multiple site listing didn’t seem to affect any other site functionality, WordPress MU or BuddyPress related. Just wanted to let you know the problem and the solution.

Best,

Steve

First of all you’ll want to get set up with an installation of WPMU and make sure that is running correctly.

It’s probably a good idea to head over to the WPMU forums where there are a lot of expect WPMU users (https://mu.wordpress.org/forums). They will be able to help you get started with MU.

Once you have that up and running, come back here and we can guide you through installing BuddyPress on top.

In your test user blog, is it just in the plugins list and needs to be activated or is it already active and shows the plugin admin menu?

You can disable Plugins in the /plugins/ dir to show up for your users under Site Options, at the bottom.

You can manually activate plugins for user blogs later.

There is a plugin (Plugin Commander) that allows you to control all the plugins in your /plugins/ dir.

If you want the plugin to work only for you main site blog, install it in the wp-content/plugins/ dir. If you have installed it in the wp-content/mu-plugins/ then it will be visible for all blogs and potentially not work correctly.

Thanks, honey.

She meant vanilla install

It’s quite likely it just has issues with WPMU, not buddypress. Some plugins do not work well with it. I’d test it on a vaniall install of WPMU first.

Hi just one question:

BuddyPress is a PLUGIN not a standalone application, is it?!

That means I can set up a WordPress-Blog and LATER add the BuddyPress-Function?!

Just asking because I have an idea for a great blog, and I am thinking about wether to wait for the official BuddyPress release or to already start my blog, and later add buddypress.