BuddyPress.org

Well, the skeleton uses WP_PLUGIN_URL because custom components should not run in the /buddypress/ directory. Since BP_PLUGIN_URL is defined in bp-core.php (line 9):

define( 'BP_PLUGIN_URL', WP_PLUGIN_URL . '/buddypress' );

if you use BP_PLUGIN_URL, it will be pathed incorrectly.

So, the question is this: Where do you have your custom component installed? It should be in /plugins/ and not /plugins/buddypress/

@Jeff, thanks for the tip. Maybe we can start a forum section listing all the plugins which have been tested by members to work without issues with BuddyPress.

@Rschilt, thanks for the info about plugin commander. I am trying it out right now. Quick question about it: After I first install plugin commander, it shows me Buddypress as the only plugin and it shows autoactivate as no. Should this be active for all members or deactivated?

I would assume activated (so that buddypress can work for everyone) but I am not sure it refers to member blogs or the community in general.

Hello, DJPaul,

My note was not an ode to IE6 (in fact, I have created several websites using simple HTML and my biggest problem was always IE6). I mentioned IE6 precisely because it’s hated and unsupported by most and yet somehow is able to solve the width problem inherent in BP.

I stressed on the problem again because (1) it’s after using RC2 and (2) I have more precise details this time. The width discrepencey I mentioned is as found in buddypress.org itself and it’s applicable to Firefox, which is my default browser for your information (I like Firebox, if I ignore their imposition of ask.com)

I am not an expert; just an observant user. If I am capable of creating a patch myself for resolving the problem, what am I doing here! And, at any rate, creating a patch is impossible unless I know where the problem lies precisely.

If nobody is going to answer, it’s ok with me.

Socialpreneur: Ok thanks.

Would I have to edit the header.php for both the home and bpmember theme? So I would add the same code to both files?

<div id="header">

<h1 id="logo"><a href="<?php echo get_option('home') ?>" title="<?php _e( 'Home', 'buddypress' ) ?>"><?php bp_site_name() ?></a></h1>



<ul id="nav">

<li<?php if ( bp_is_page( 'home' ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>" title="<?php _e( 'Home', 'buddypress' ) ?>"><?php _e( 'Home', 'buddypress' ) ?></a></li>

<li<?php if ( bp_is_page( BP_HOME_BLOG_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php bp_home_blog_url() ?>" title="<?php _e( 'Blog', 'buddypress' ) ?>"><?php _e( 'Blog', 'buddypress' ) ?></a></li>

<li<?php if ( bp_is_page( BP_MEMBERS_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_MEMBERS_SLUG ?>" title="<?php _e( 'Members', 'buddypress' ) ?>"><?php _e( 'Members', 'buddypress' ) ?></a></li>



<?php if ( function_exists( 'groups_install' ) ) { ?>

<li<?php if ( bp_is_page( BP_GROUPS_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_GROUPS_SLUG ?>" title="<?php _e( 'Groups', 'buddypress' ) ?>"><?php _e( 'Groups', 'buddypress' ) ?></a></li>

<?php } ?>



<?php if ( function_exists( 'bp_blogs_install' ) ) { ?>

<li<?php if ( bp_is_page( BP_BLOGS_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_BLOGS_SLUG ?>" title="<?php _e( 'Blogs', 'buddypress' ) ?>"><?php _e( 'Blogs', 'buddypress' ) ?></a></li>

<?php } ?>



<?php do_action( 'bp_nav_items' ); ?>

</ul>

</div>

If I wanted to add another menu-link would I have to add something like this to both header.php files? Saying the new page was called ‘pagename’:

<?php if ( function_exists( 'bp_pagename_install' ) ) { ?>

<li<?php if ( bp_is_page( BP_PAGENAME_SLUG ) ) {?> class="selected"<?php } ?>><a href="<?php echo get_option('home') ?>/<?php echo BP_PAGENAME_SLUG ?>" title="<?php _e( 'Pagename', 'buddypress' ) ?>"><?php _e( 'Pagename', 'buddypress' ) ?></a></li>

<?php } ?>

Or is this wrong? Just wanna make sure I do it right.

I renamed those two files, placed the code in them that I wanted to work sitewide, and uploaded back to the css folder of the bphome directory. Nothing happened. Maybe you could give me a little more direction about exactly where these files should go? I’d sure appreciate it!

I see those files (site-wide-sample.css and custom-sample.css) in the bphome folder. If I change those, do I put them back to the places where they currently reside? Does the bphome folder control the look of these other parts of the site? I’m confused about which files control which parts of the site. If there is some kind of structural documentation on BuddyPress, showing which parts files are controlling, that would be great. It isn’t transparent enough from the structure of the files themselves (at least not for a non-programmer). Thanks!

I didn’t notice status changed to resolve, but it’s not. It’s somewhat resolved because I remove those lines.

I have a perfect working WPMU 2.7.1, and all I want to do is to add those lines as wordpress mu’s tutorial site suggests for security reason. I don’t need BBPress. I had tried installed BBPress before when I first installed BuddyPress. I didn’t get BBPress worked with BuddyPress so I ditched BBPress.

Clearly I have a working WPMU 2.7.1, and working BuddyPress 1.0 (final). Though my only problem is by adding those lines, the logout link won’t work properly. It’s obvious it has to do with cookies and sessions.

So by removing those lines meaning I’m not doing exactly like WordPress MU tutorial suggests. So it’s not resolved. I wonder because what I did with BBPress before and then decided not to use BBPress by removing it has an after effect that affects my situation now? I remember that BBPress requires you to mess around with cookies and stuffs like that.

oh JJJ – to answer your Q, my username / login comes from wordpress.org so the integration works as far me logging in but there is clearly a problem with the way it is functioning. My inkling here is bug, perhaps an enhancement request. while is doesnt bother me per se it is a problem and requires a “fix”.