[@burtadsit Participant 17 years, 7 months ago]

Seems you have answered your question sgrunt.

[@burtadsit Participant 17 years, 7 months ago]

zanzoon, if the ownership rights is the problem then I can’t help you. egerrits’ solution may be the only one available. There’s something wrong with having to rely on a host tech support people ‘being nice’ to solve what shouldn’t be a problem in the first place. (sigh)

Try it out egerrits’ way zanzoon.

[@burtadsit Participant 17 years, 7 months ago]

bobman024, I’m kinda lost here. What plugin are we talking about? bpGroups? Download the latest at: http://code.ourcommoninterest.org/2009/02/14/buddypress-group-forums-for-bbpress/

I just downloaded that ver and set it up again. Activates and operates.

[@burtadsit Participant 17 years, 7 months ago]

sgrunt, ya I guess you wouldn’t need to mod the widget code, just the theme code. hmm. Well if Andy says it’ll go away by updating to latest trunk then it will. Warning! The theme directories have changed. See: https://buddypress.org/forums/topic.php?id=1675

[@burtadsit Participant 17 years, 7 months ago]

No activity here for three days, turning out the lights in the room.

[@burtadsit Participant 17 years, 7 months ago]

I new this issue was familiar: https://buddypress.org/forums/topic.php?id=976

Nobody seems to have figured out why this is happening. Please describe your configuration. subdirectory/subdomain, wpmu installed in a sub dir or the root, what ver of wpmu, …

We are never gonna figure this out otherwise.

[@burtadsit Participant 17 years, 7 months ago]

Check the permissions and more importantly the ownership rights for the stuff in /blogs.dir/1/files/avatars/1

Everything from /wp-content down. Does your apache user have create rights in that dir chain? apache might be ‘nobody’ or ‘apache’ or something else entirely. Depends on your server setup.

Or like nicola suggests you’ve got some other js loading that is conflicting with the cropper.

[@burtadsit Participant 17 years, 7 months ago]

Your users have to register with wpmu and that means the main blog initially. If all you want is for them to be registered users in your community blog automatically then try this plugin: http://code.ourcommoninterest.org/2009/01/02/community-and-group-blogs-in-a-can/

Activate and configure that plugin on your community blog and when your users visit the blog for the first time they will become registered users at whatever level you set in the admin screen for the plugin.

I think that is what you want.

[@burtadsit Participant 17 years, 7 months ago]

Original question resolved. vskylabv open a new topic if you still need help.

[@burtadsit Participant 17 years, 7 months ago]

I can’t reproduce this. I know this issue has cropped up before. I remember it now. Did you update your themes also?

[@burtadsit Participant 17 years, 7 months ago]

You can find these people in the member directory and ‘request friendship’ there or go to their profile and do it.

[@burtadsit Participant 17 years, 7 months ago]

You’ll have to modify the member theme functions that display the fields in the profile. That gets generated in: /buddypress-member/profile/profile-loop.php

by the function: bp_the_profile_field_value() in /mu-plugins/bp-xprofile/bp-xprofile-templatetags.php

There’s a filter in there that you can hook: echo apply_filters( ‘bp_the_profile_field_value’, $field->data->value, $field->type, $field->id );

So that you can detect these specific fields and change what gets generated by bp.

[@burtadsit Participant 17 years, 7 months ago]

Let’s see, are you talking about all the links in the admin menu bar, the member theme or the home theme? It seems you want to know where *all* of them are.

(sigh) Ok.

The admin bar code is in: /mu-plugins/bp-core/bp-core-adminbar.php

The code for the member theme is in: /wp-content/member-themes/buddypress-member

The code for the home theme is in: /wp-content/themes/buddypress-home

[@burtadsit Participant 17 years, 7 months ago]

You should ask johnjamesjacoby about this migrate issue. He’s done something like that recently. I think the answer is you need to export your data, using phpmyadmin or with the native export/import tool in wp.

http://www.techtraction.com/2007/07/30/move-or-backup-wordpress-data-with-the-built-in-importexport-feature/

Lots of stuff if you google ‘wordpress export’, ‘wordpress import’

[@burtadsit Participant 17 years, 7 months ago]

Check the permissions and more importantly the ownership rights for the stuff in /blogs.dir/1/files/avatars/1

Everything from /wp-content down. Does your apache user have create rights in that dir chain? apache might be ‘nobody’ or ‘apache’ or something else entirely. Depends on your server setup.

[@burtadsit Participant 17 years, 7 months ago]

You’ve modified the members and groups widget code. Did you also change the ajax handler code? bp_core_ajax_widget_members() for example in /bp-core/bp-core-ajax.php

[@burtadsit Participant 17 years, 7 months ago]

Check the permissions and more importantly the ownership rights for the stuff in /blogs.dir/1/files/avatars/1

Everything from /wp-content down. Does your apache user have create rights in that dir chain? apache might be ‘nobody’ or ‘apache’ or something else entirely. Depends on your server setup.

[@burtadsit Participant 17 years, 7 months ago]

Yep. That’s gotta be it John. If that’s missing the whole thing changes. Practicing the ‘he who is loudest is right’ approach to support doesn’t seem to be working for me. Perhaps I should switch back to actually investigating things instead?

[@burtadsit Participant 17 years, 7 months ago]

oh. (sigh) sorry.

[@burtadsit Participant 17 years, 7 months ago]

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

[@burtadsit Participant 17 years, 7 months ago]

vskylabv, it would help if we had an url to your site.

[@burtadsit Participant 17 years, 7 months ago]

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

[@burtadsit Participant 17 years, 7 months ago]

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

[@burtadsit Participant 17 years, 7 months ago]

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.

[@burtadsit Participant 17 years, 7 months ago]

The dreaded white screen of death is a symptom of a fatal error occurring in php code. If you can’t get at your error logs then we can’t help you. There has to be something in there.