You seem to have mu configuration problems. None of your subdomains can be reached. It’s best to get mu setup, configured and working properly before installing bp. Test mu blog creation and reachability, create and edit posts, make comments. Get comfortable with mu first.
It will make installing and configuring bp a whole lot easier. I played with mu for a month before I felt comfortable with it.
What type of host are you on? Shared, DV? Looks like you need to do some DNS tweaking for your subdomains to work.
those are set to 755. I literally went through every single file twice and all buddypress files are 755.
@bloggerhistory Check the permissions in /wp-content/themes/buddypress-home/css
Those 3 files and the css dir should be 755.
I am still having this problem on my site:http://bloggerhistory.com. I have gone through and changed all buddypress files to 755.
All that after a *Fresh install of the latest versions of both WPMU & Buddypress. Did I miss anything else?
heh’ sorry, I found it in bp-core-adminbar.php
Took out:
if ('Admin' == $role) {
echo '<li><a>siteurl . '/wp-admin/themes.php">' . __('Switch Theme', 'buddypress') . '</a></li>';
and the “}” on line 163.
Buddypress started working on http://seminaritaifa.org
Theme customization is not 100% ready but we decided to put it up inproduction
borkweb I love the uber-geeks design and colors. How do you get those colors intothe theme???
1 and 3 are fix, I had activated the theme but not selected it, Doh.
My mistake. I see that invalid path question here alot and you are the first to say it was trying to access Groups. Usually it goes: “I’m having a problem fix it for me”. I just saw the path and plugged in the standard response. Well, lets go look at that problem then. 
This is happening in the member theme when you try to access a group where? Me > Groups > My groups > pickagroup?
That’s about the only place in the member theme you can pick a group. What versions of everything are you running.
Line 74 in mu 2.7 trunk is a comment.
I know it’s not a valid path, but I can’t find the invalid config. btw, I suspect it’s a bug since this only happens in /groups/some-group and not on other parts of BP that are using the member theme
For now I’ve redirected php errors to a log file by adding this to the top of wp-config.php:
@ini_set('log_errors','On');
@ini_set('display_errors','Off');
@ini_set('error_log','/FULLPATH/log/php_error.log');
You have a configuration problem. /wp-content/member-themes/buddypress-home/… is not a valid bp path.
Thanks, I guess I was reading an old readme or something.
I got some new issues now but I will start a different thread.
I had the same problem with my member theme until I tracked down this post: I was putting the member theme in the themes directory along with BuddyPress Home theme. What threw me was the fact that in the pre beta releases the member theme WAS located in the themes directory. A bit confusing, but an easy fix.
The dire warning means it can’t load up the member theme because as you pointed out, it isn’t in the right spot. It needs to be in /wp-content/member-themes.
The home page theme needs to be selected as your theme if you want it to be the theme on that blog.
@fserer Nice work on integrating bp into your theme. Very slick.
Both the member adminbar and the home theme logout options take you back to the originating url. Upgrade to the latest trunk or the beta download.
Here’s the code which can be found in the BP home theme header:
<?php if ( function_exists(‘wp_logout_url’) ) : ?>
/ ” alt=”<?php _e( ‘Log Out’, ‘buddypress’ ) ?>”><?php _e( ‘Log Out’, ‘buddypress’ ) ?>
<?php else : ?>
/ “><?php _e( ‘Log Out’, ‘buddypress’ ) ?>
<?php endif; ?>
What I did was added this code to my theme’s functions.php file:
<?php function _user_name()
{
global $userdata;
get_currentuserinfo();
echo $userdata->user_login;
}
?>
Then, you construct your links like this:
http://yourdomainhere.org/members/<?php _user_name(); ?>/profile
Just swap out “profile” for whatever you want to link to.
those paths sounds good
Here are my paths:
wp-content/member-themes/buddypress-member/
wp-content/themes/buddypress-home/
usually do not put buddypress home in member-themes/
have you tried bbpress and wpmu inegration ?
burtadsit, I am totally confused and brain dead.
Excuse my ignorance.
Here are my paths:
wp-content/member-themes/buddypress-member/
wp-content/themes/buddypress-home/
From install instructions:
Move the “buddypress-home†folder to “wp-content/themes/†and move the “member-themes†folder to “wp-contentâ€.
You should now have the following folder locations “wp-content/themes/buddypress-home†and “wp-content/member-themes/buddypress-homeâ€.
How does buddypress-home get in both paths? See, I’m brain dead.
Once again. You have a config problem. This is the same path you mentioned in another message as having a different problem. I explained there also that:
/wp-content/member-themes/buddypress-home/…
Is not a valid path for bp.
The only thing under /wp-content/member-themes is /wp-content/member-themes/buddypress-member/…
Boy, I thought this was going to be a go until I got this: when trying to create a group:
Warning: require_once(/home/ramona/public_html/wp-content/member-themes/buddypress-home/index.php) [function.require-once]: failed to open stream: No such file or directory in /home/ramona/public_html/wp-includes/theme.php on line 822
Fatal error: require_once() [function.require]: Failed opening required ‘/home/ramona/public_html/wp-content/member-themes/buddypress-home/index.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/ramona/public_html/wp-includes/theme.php on line 822
I’m logged into buddypress as the admin
I just installed fresh this morning – buddypress-combo
Fresh install of bbpress-1.0-alpha-4
Fresh install of wpmu trunk r1574
As a side note I also got an error trying to access user account, but I’ve posted that elsewhere here.
It looks like it’s almost pudding, but not quite. What am I missing?
Hi wardeh. Are you just gonna skin the home theme? In that case yes. custom-styles.css is what I would use. If I remember correctly it gets fired up last in sequence so it overrides the other css.
Yep. Just looked. Both the home and member themes look for custom.css and load it last.
