BuddyPress.org

We don’t have sufficient information to provide any assistance. Please answer these questions:

1. Which version of WPMU are you running?
2. Did you upgraded from a previous version of WPMU, and if so, from which version and how?
3. Did you have WPMU functioning properly before installing and upgrading BuddyPress?
4. Which version of BuddyPress are you running?
5. Did you log in as site admin in WPMU’s backend and activate BuddyPress?
6. Do you have any plugins other than BuddyPress installed and activated?
7. Are you using the standard BuddyPress themes or custom themes?
8. Are there are errors in your server’s log files, and if so, what are they?

Okay, before we can assist further, we need more information. Please answer these questions:

1. You’re positive that you’re running WordPress Mu and not single-version WP?
2. Assuming the answer to number 1 is yes, then did you upgraded from a previous version of WPMU, and if so, from which version and how?
3. Did you have WPMU functioning properly before installing and upgrading BuddyPress?
4. Which version of BuddyPress are you running?
5. Did you log in as site admin in WPMU’s backend and activate BuddyPress?
6. Do you have any plugins other than BuddyPress installed and activated?
7. Are you using the standard BuddyPress themes or custom themes?
8. Are there are errors in your server’s log files, and if so, what are they?

you just need to edit your Members-Theme and move the “post to wire box/function” to where you want it.

bp-themes/buddypress-member/profile/index.php

on the very bottom of the page, you’ll see an IF statement “bp_wire_get_post_list”

just move that where you want it, be sure to keep it in the right DIVs

Hi again

I made some mistakes:

– asume that the upgrade from RCx to v1 was simply copying files over the old ones and didn’t noticed the change in the setup procedure to /wp-content/plugins/buddypress

– Also is posible that as my MU base was 2.7 it messed a bit too

– Tampering the themes fields in the db with a non ortodox setup

I started the intall process all over and it works fine again.

As a final test I tried to swap the old DB for the new one but I get again messages like the BP_PLUGIN_DIR path.

Just if helps …

Regards,

I’m having the same issue but with Activities when starting up in:

Fatal error: require() [function.require]: Failed opening required ‘BP_PLUGIN_DIR/bp-activity/bp-activity-classes.php’ (include_path=’.:/usr/share/php:/usr/share/pear’) …www/wp-content/mu-plugins/bp-activity.php on line 14

I “ugraded” from RC1 to v1 but failed. Then I removed everything except WPMU & wp-config.php, as the DB was ok. Copied BP, moved the themes and got the message.

I tried to reset the themes in db to bpmember and bphome without success.

you would edit your bp bp-themes/ or theme/buddypress-home/

depending on where you want it.

you could also add the “tweet” stuff directly to the functions.php file

/themes/buddypress-home/home.php

(the above is the home page, which calls the left,center,right sidebars)

you could manually insert your code there.

there’s a few different way to do that…. some would say creating a plugin/function/bp-custom code is the best

Just replaced the 6 instances of get_option(‘home’) in header.php of my member blog theme with $bp->root_domain as described.

Don’t see any difference in the behavior of the site.

Really impressed with delsolownersclub wow. great work.

I’d love to turn this into a procedure for the community, but I don’t know how to do it yet. Stuck here too: https://buddypress.org/forums/topic.php?id=1632&page=2&replies=43#post-14553

Best,

Dainis

I remember Andy said he would fix this in a different post. Althrough I do not think this has been resolved in the latest skeleton theme yet.

Jfcarter-

You do have the calls to the buddybar as I outlined in the second post in this thread, correct?

Are you using a customized bbPress theme? If so, switch to the default bbP theme, add in the necessary code as detailed in this thread, and see what happens.

Not tested, but this would probably do it (put it in a plugin and activate it or add it to your theme’s functions.php file):

<?php

function disable_name_change( $data ) {

if ( 1 == $data->field_id )

$data->field_id = false;



return $data;

}

add_action( 'xprofile_data_before_save', 'disable_name_change' );

?>

We do not have sufficient information to provide any assistance. Please provide the following:

1. Which version of WPMU are you running?
2. Did you upgraded from a previous version of WPMU, and if so, from which version and how?
3. Did you have WPMU functioning properly before installing and upgrading BuddyPress?
4. Which version of BuddyPress are you running?
5. Did you log in as site admin in WPMU’s backend and activate BuddyPress?
6. Do you have any plugins other than BuddyPress installed and activated?
7. Are you using the standard BuddyPress themes or custom themes?
8. Are there are errors in your server’s log files, and if so, what are they?

Right, that\’s interesting.

I\’m thinking now along just having a on/off setting for user\’s that identifies them as a \’special\’ member. This would involve a checkbox on the user page visible only to Admins and then some kind of conditional tag for dynamically altering the theme (e.g. adding a star next to a member\’s name).

Any thoughts?

Edit: in fact, this could be done with WP’s usermeta functions maybe?

you can check out the privacy settings ( I would like my blog to be visible only to registered users from blog community ) then maybe edit the log-in page.

Andrea,

No I think I am using the other older one. (I came across DeannaS’ but for some reason forum discussions convinced me that it was still a work in progress.) Ill switch over and try it out now. Thanks.

You’ll want to put this at the top of bb-config.php:

if ( !defined('ABSPATH') & !defined('XMLRPC_REQUEST')) {

define('WP_USE_THEMES', false) ;

include_once( '/your/absolute/path/to/domain/wp-blog-header.php' );

header("HTTP/1.1 200 OK");

header("Status: 200 All rosy") ;

}

The & should be just the &