BuddyPress.org

No I don’t see the problem. If there is a problem, only logged in users can see it. Can you give me a demo/test login username and password?

Well, change what field? The user Full Name field?

About to start a danish translation of BuddyPress. Currently considering to use either LaunchPad or Pootle as our collaboration tool.

Anyone know if Dreamcolor expects to initiate the LaunchPad project:

https://translations.launchpad.net/buddypress or release the ownership, for others to use it?

Suggestion: why don’t we settle on the same tool to use, eg LaunchPad – would make it easier for other to take part of the work.

I did this on this site, and like this:

function register_user_as_contributor($username) {

global $bp, $wpdb;



$user_id = bp_core_get_userid_from_user_login( $username );



if ( !$user_id )

return false;



$role = maybe_unserialize( get_usermeta( $user_id, $wpdb->base_prefix . '1_capabilities' ) );



if ( is_array($role) )

$role = $role[0];



if ( !$role || '' == $role || 'subscriber' == $role ) {

$role['contributor'] = 1;



update_usermeta( $user_id, $wpdb->base_prefix . '1_capabilities', $role );

update_usermeta( $user_id, 'primary_blog', 1 );

update_usermeta( $user_id, 'source_domain', 'buddypress.org' );

}

}

add_action( 'wp_login', 'register_user_as_contributor' );

I’m sure there is another action you can use so it doesn’t run on every login, but this works.

I can usually recommend some solution that doesn’t require modifying the core. In this case I just can’t. It looks to me like the only way to get years beyond 2009 is to do this:

/buddypress/bp-xprofile/bp-xprofile-classes.php

Line # 567 is:

for ( $i = date( ‘Y’, time() ); $i > 1899; $i– ) {

Change that to:

for ( $i = date( ‘Y’, time() ) + 5; $i > 1899; $i– ) {

You mean top left of theme? That’s an image – you’ll find it in /wp-content/bp-themes/buddypress-member/images/logo.gif.

Ninh-

I’ve looked at your site and of course cannot duplicate the problem without logging in. But, that’s okay.

You mention that you’re using a custom theme. Read the first post in this thread, paying close attention to the parts that talk about custom themes. Also, there are more posts within this thread that discuss theme issues that could apply.

It appears that you are still using BuddyPress 1.0_RC1. I cannot remember if any of these issues apply to RC1. Perhaps someone with longer BP experience can chime in.

There’s nothing confusing about this at all.

We’ve got wpmu installed on a linux type subdomain using the subdirectory blogs option with bp’s home theme running on a blog id other than the default root blog id of ‘1’ using beta versions of both wpmu and bp including a new restriction from bp that it be installed in /plugins/buddypress and activated sitewide with a new mechanism that replaces the old /mu-plugins scenario.

lol. Time for a nap.

Okay, putting aside the subdomain versus subdirectory issue for a second, you state that:

…the bp link in the menu works but where is says “disbale components using below form” nothing shows

It sounds like BuddyPress is not activated. With the 1.0_RC2 changes, BuddyPress is now considered a single WPMU plugin. You must first login to the WPMU backend as site admin and then go to Plugins > Installed and make sure that BuddyPress is activated.

Once it’s activated, a new menu group is created at the bottom of the menu tree called “BuddyPress”. You click on BuddyPress > Component Setup and you should see that all the BP components are enabled by default. It is in this admin screen where you can enable and disable individual components.

If you’ve already activated BuddyPress, then something is clearly wrong. Have you double checked to make sure that you copied all the BP component files and folders (minus the theme folders) into the /wp-content/plugins/ folder? Did you install the BP suite into the /wp-content/mu-plugins/ folder instead?

If the BP install locations and files are in their proper place, then I would recommend deactivating BuddyPress then deleting the entire BP directory and try reinstalling the BP plugin suite again and see what happens.

Okay, all you developers out there. I’m sure you have an opinion. We’ve only heard from six members and I know there are more of you lurking behind the code somewhere!

Come on out. Tell us your thoughts and opinions!

Danielfelice-

Okay, a few more questions:

1. Are there any errors being reported in the error logs? If so, what are they?
2. Are you using the default BuddyPress themes with no changes at all?
3. Did you use the new WPMU config file, or a config file from an older version?
4. Is buddyPress-home theme installed in /wp-content/themes/ ?
5. Is buddyPress-member theme installed in /wp-content/bp-themes/ instead of /wp-content/member-themes/ ?
6. Did WPMU work fine before BuddyPress was installed and activated?
7. Do you have any WPMU plugins other than BuddyPress installed? If so, have you tried deactivating them to see if that makes a difference?

i would do that, but under donations not payment

Home theme:

wp-content/themes/buddypress-home/

Member theme (for RC1):

/wp-content/member-themes/buddypress-member/

Is there a way to replace the img with just the word ‘Home’ in the same font/style as the rest of the navigation?

I\\\’ve tried replacing this:

\\\’ **** Default BuddyPress admin bar logo ********

function bp_adminbar_logo() {

global $bp;

echo \\\’root_domain . \\\’\\\”><img id=\\\”admin-bar-logo\\\” src=\\\”\\\’ . apply_filters( \\\’bp_admin_bar_logo_src\\\’, site_url( MUPLUGINDIR . \\\’ … admin_bar_logo.gif\\\’ ) ) . \\\’\\\” alt=\\\”\\\’ . apply_filters( \\\’bp_admin_bar_logo_alt_text\\\’, __( \\\’BuddyPress\\\’, \\\’buddypress\\\’ ) ) . \\\’\\\” >\\\’;

}\\\’

with this:

\\\’ **** Default BuddyPress admin bar logo ********

function bp_adminbar_logo() {

global $bp;

echo \\\’root_domain . \\\’\\\”>Home\\\’;

}\\\’

That should only replace the img with text, but for some reason it messes up the entire top line navigation. Apparently there\\\’s some code mixed in with the already overcomplicated img link that\\\’s required for what follows after. What and why?!

Aaarrrggghhh…. I give up. It’s impossible to show the code without it becoming a mess.

[code 1="a" 2="bit" 3="to" 4="avoid" 5="escaping" 6="mess" language="modified"][/code]

Aaarrrggghhh…. I give up. It’s impossible to show the code without it becoming a mess.

The main (home) page would have to use a customized theme that is simply a splash page (spalsh screen) that gives basic information about your site and a place to login and sign up.

Once a user has logged in, it would then go to the BuddyPress home page–which you could also customize if you want.

Read this thread for how to Secure components from non logged in users.