BuddyPress.org

i’m sure it depends on the version your using: i was getting mad to solve it in my local installation with no success: i thought it was a fault of my custom theme. Then i’ve tried my custom theme on my second local installation and all worked fine. I don’t remember how to see the current version number of buddypress, if i know how to see it i can tell you what is the working version.

You can currently use the bbGroups plugin by BurtAdsit to do this with group forums. He’s paused integration for other Extended Profile fields and non-group forums for now, but that is the closest integration available currently.

Take a look over at http://code.ourcommoninterest.org/

Science Content!

The problem with doing it any other way right now, is that without grabbing and caching forum specific BuddyPress profile info and putting it into a convenient user_meta array, it would require an additional query into the database for each user that you want each piece of info for. So lets say you not only want the avatar, but their fullname, and another piece of profile info that you’ve made up. That’s three queries a person, per post, per page. A page with 10 posts just gave you 30 extra queries. The bbGroups plugin works great to counter act this, but I’ve been the primary beta tester experiencing hiccups and Burt has patiently been trouble shooting with me to figure out why. The past week life has sort-of halted my ability to test, but it is a priority for me to address.

unfortunately this did not work for me, i’d also like to use one wpmu install and run multiple separate domains with buddypress on a subdomain and bbpress, using the inove theme.

see my post on wpmu forum

https://mu.wordpress.org/forums/topic.php?id=11695#post-70149

Warning: require_once(/home/public_html/wp-content/member-themes/buddypress-member/index.php) [function.require-once]: failed to open stream: No such file or directory in /home/morisus/public_html/wp-includes/theme.php on line 822

Fatal error: require_once() [function.require]: Failed opening required ‘/home/public_html/wp-content/member-themes/buddypress-member/index.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/public_html/wp-includes/theme.php on line 822

How do we address the path issue?

(Sigh) it’s okay, but next time we’re taking this to fisticuffs!

oh. (sigh) sorry.

Can I just say that you have made a excellent choice in pmwiki. Have you thought about making group wikis?

http://allthingschurch.org/

Thank you for your reply. As I noted earlier, I’m already running a WordPress blog network with active members. Incidentally, the README.txt file for WordPress actually uses the directory /blogs as an example:

* If you want to have your WordPress MU installation in its own

subdirectory on your web site (e.g. http://example.com/blogs/),

rename the directory wordpressmu to the name you’d like the

subdirectory to have and move or upload it to your web server.

For example if you want the WordPress MU installation in a

subdirectory called “blog”, you should rename the directory called

“wordpressmu” to “blogs” and upload it to the root directory of your

web server.

I imagine this may be a problem for others who went in this direction. Are you saying that those of us in this situation are out of luck with BuddyPress unless we reinstall and try to import all of our users’ blogs into the new site?

Thanks again, I do appreciate your time on this.

Don’t install BuddyPress in /blogs

Make sure you are starting your customization with the latest trunk brad85. I don’t know what ver of bp’s home theme you are customizing. In the latest trunk there are two functions that control what goes on in the login/signup buttons. The bp home theme header.php file calls <?php bp_login_bar() ?>. In that fn it calls bp_signup_page() which you see below:

function bp_has_custom_signup_page() {

if ( file_exists( WP_CONTENT_DIR . ‘/themes/’ . get_blog_option( 1, ‘template’) . ‘/register.php’) )

return true;

return false;

}

function bp_signup_page( $echo = true ) {

global $bp;

if ( bp_has_custom_signup_page() ) {

if ( $echo )

echo $bp->root_domain . ‘/’ . REGISTER_SLUG;

else

return $bp->root_domain . ‘/’ . REGISTER_SLUG;

} else {

if ( $echo )

echo $bp->root_domain . ‘/wp-signup.php’;

else

return $bp->root_domain . ‘/wp-signup.php’;

}

}

Unless you don’t have the register.php file in /themes/<your theme>, or you’ve somehow altered the header calling sequence so this code doesn’t run, then it should work fine. The signup button should not have anything to do with wp-login.php

This is about the MSM plugin. Turning off the light.

Burt, I was agreeing with you.

I see that spot in wpmu code. What does something hard coded in wpmu have to do with bp?

get_bloginfo(‘wpurl’).”/wp-admin/profile.php

should be replaced with a call to: bp_core_get_userurl($bp->loggedin_user->id) which is the url to the currently logged in user. You’ll have to declare ‘global $bp;’ someplace before that in the code.

“i have the BuddyPress Home Theme set to active and the other set to no.”

here you are talking bout the “admin themes” where admin can approve or not themes that can be activated. But it is not the activation: go to Design / Themes and click on the selected theme you want to be active.