BuddyPress.org

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.

It has to be somewhere between the opening and closing head tags

<head></head>

It cannot go in the body section.

Also, I assume that you\’ve followed the standard directory structure for the themes:

'/wpmu/wp-content/themes/buddypress-home

My mistake. You need to put the forward slash back since bloginfo(‘template_url’) does not append it.

You have the favicon.ico file in the root of the buddypress-home folder?

Now we’re talking Jeff.

More questions?

1. By latest WPMU, do you mean latest public release?
2. Have you customized the theme in any way?
3. Have you tried disabling all but the BuddyPress plugins?
4. Where exactly do you have the BuddyPress plugins installed?
5. Have you tried re-uploading from scratch?

These are the supported languages:

http://alexgorbatchev.com/wiki/SyntaxHighlighter:Brushes

The issue was initially presented as a well-defined problem:

BuddyPress developers need a common place to share code snippets

Now, the conversation has transformed into a bigger-picture discussion. That is always good in my mind.

Burt and Andy bring up valuable points. As Burt points out, we are on the verge of something interesting. We have an opportunity to use the social-networking tools of BuddyPress to create something unique and wonderful in the developer community. Andy offers very specific, compelling reasons on why and how we should indeed use those tools.

So, I propose that we need to reframe the originally-stated issue like this:

What is the best way for BuddyPress developers to leverage the power of BuddyPress to create a vibrant, useful developer resource?

@Stefk, try Burtadsit’s solution.

Private members and groups sections should be a core feature of Buddypress imho.

I’ll reply to the name issue here also. The group names and descriptions can be arbitrarily long and can trash the theme layout in bbpress. These are two different software packages Elody and I chose to be as minimally invasive as possible. I left the forum name and description up to the bbpress/wpmu admin’s discretion.

I didn’t think that a site admin would be too happy to have the theme broken by a long group name.

I included a way out also. The name and description of the group are pulled over to bbpress and are available as template tags for you to use.

oci_group_name()

oci_group_description()

It would make sense to have a searchable blog for such code snippet creations. The restrictions on proper searching in bbPress makes it difficult to find things. I get better results searching google to find things I know exist in these forums. That is where a blog would be way better

Trent

From the forums installation-readme.txt:

11. Enable user switching in bbPress by copying the following line of code into your bbPress

bb-config.php file:

$bb->bb_xmlrpc_allow_user_switching = true;

Needs to be in your bb-config.php

A helpful topic here: https://buddypress.org/forums/topic.php?id=471

I too am in favor of the “another blog on this site” option.

Having thought about it more – my vote would be another blog on this site.

For a few reasons:

1. People can use the same login, and therefore comment without being spammed or moderated.

2. We can promote regular BuddyPress community members to \”snippit creator\” status.

3. We can track all the snippets in activity streams.

4. We get nice buddypress.org permalinks for every snippet.

5. RSS.

Mascix, this is really a WPMU question. I suggest searching the WPMU forums and if you can’t find the answer, then start a new thread there.

DJPaul-

Just a couple quick thoughts specific to BuddyPress:

1. Has x number of friends. Triggered at each admin-set interval such as 25, 50, 100.

2. Has joined x number of groups.

3. Has started x number of groups.

4. Has contributed x number of group wires

Each of these are basically milestones that could be set in the backend. As each milestone (achievement) is reached, a new icon could be displayed in the user’s profile.

Nothing fancy. Just quick ideas.