Hi, thanks for the nice support. Yes I know it is for developing. I was wondering, thinking a example should work. But it was my stupidity. There was an old bp-dev plugin example in my plugin folder I think that curse the problem.
Thanks and Sorry
If it’s not showing on all your blogs then check the setting of: wpmu back end > BuddyPress > General Settings > Hide admin bar for logged out users?
If some themes are still not showing the admin bar then that means they are not written to calll wp_footer() in the theme itself.
this post might help you answer some of your questions… https://buddypress.org/forums/topic.php?id=3204
Anything new since two months ago? There have been many changes to BuddyPress over that time!
Have you searched the forum and read this thread
If so, then you need to provide more of an explanation than “Having the same problems with avatars”. That tells us exactly nothing to begin the process of providing support. Please see this thread as well.
I will say that I have elected to delete some lines of code to remove some functions in the core files but they aren’t super critical, in my opinion.
Okay, as I’m sure you know, this type of sentence scares all of us who try to offer support. 
The real question is this:
If you boil everything down to the lowest, common denominator (LCD), does everything work. This means using BuddyPress without any core mods, using the default themes, and not running any other plugins in WPMU except BuddyPress.
If everything works, then this is an issue caused by something you are doing. If you still have this problem, then you need to talk with your hosting firm or system admin (if you are in a business/institutional setting) because it could have something to do with your server setup (DB server maybe).
But, if everything works as it should when you’ve distilled the WPMU/BuddyPress install down to the LCD, then it clearly is something you’re doing. It could be your core hacking, the single-sign-on coding, a 3rd-party plugin conflict, any combination of changes. You need to go back to the bare bones foundation and then start adding stuff back, implementing your changes one at a time and throughly test in between each new change.
The inner workings of the e-mail spam detectors are strange and mysterious. You are probably right in that having your mail sent by a server on a domain hostname different than the domain specified in the “from” field in the mail (your domain) counts against them. I’d set up a big “check your junk mail” blurb as suggested above, and recommend your members to mark all BuddyPress e-mails as “not spam”.
Same problem here – the duplication error that is.
The strange part is that it just recently showed up, everything worked just fine earlier.
—
Fatal error: Cannot redeclare bp_core_signup_set_headers() (previously declared in /var/www/www.soldaterliv.com/www/wp-content/plugins/buddypress/bp-core/bp-core-signup.php:4) in /var/www/www.soldaterliv.com/www/wp-content/plugins/buddypress/bp-core/bp-core-signup.php on line 1
—
Many of my users complain about the confusing nav of the default theme but since I am still trying to get all features of my site to work, I haven’t had a chance to spend time on the theme aspects. I would love to be able to incorporate aspects of the buddypress.org theme on my site. Hoping copypress is able to release the theme 
In a similar post Andy said that it was basically just CSS changes if somebody wanted to give it a go. He didn’t offer up the code, but basically said go for it, it somebody wanted to take the time to do it…
The BP_ENABLE_MULTIBLOG option works fine on my install using subdomains.
where is this setting located?
It’s the first I have heard of this function
I want this theme as well, is this a go?
The BP_ENABLE_MULTIBLOG option works fine on my install using subdomains.
Do you have any custom code in bp-custom.php or plugins that redirect the user after login active? The normal behavior for login from that member theme sidebar area is to drop right back into to the same blog you logged in from.
In 1.0.1 I tried the login from the member theme sidebar area and if you have the bp root blog defined properly it works just fine. I assigned another blog as the BP_ROOT_BLOG and everything bp stopped working on blog id 1 as expected. It works just fine from blog id 17 that I switched it to.
I can only comment on how bp 1.0+ operates. What version bp? I don’t know that the image upload or login problems have anything to do with what we are talking about. When you select one of the directories such as members, groups or blogs from the theme main nav, does it run the directories properly? If the answer is yes to that and your member theme works properly then bp is happy with whatever blog id it thinks you’ve defined as it’s root blog.
There are also two different types of image uploads in bp/wpmu. bp’s avatars and the blog post images that are associated with them. Which one are you referring to?
Ok, I wasn’t clear enough:
I installed wpmu using subdomains.
I had Nicola install buddypress onto my main domain for mu. Then after seeing the roadmap and a few other notes, I decided to move buddypress from the foreground on the homepage to a subdomain so that I could use a production ready theme for my site.
I created a new blog ‘community’ and turned on the buddypress theme. I also went into bp-custom.php and inserted your code, replacing the X with the blog id# (I had also tried applying the code change to wp-config.php as well, did not work either)
Basically bp is not picking up the fact that it is now blog id #30 instead of blog id#1, hence the broken login and also the image upload problems that popped up after ‘moving’ bp off the root blog.
I hope this is more clear
bbpress RC2 and RC3 integration is broke. See: https://buddypress.org/forums/topic.php?id=3199
Neither one of us in that thread had any success. I’m particularly proud of my discovery of the true nature of the relationship between bp/wpmu/bbpress when it comes to integrating the three:
http://hyperphysics.phy-astr.gsu.edu/hbase/forces/imgfor/fforcon.gif
I changed the title to indicate that it’s here that the problem exists.
You can indicate to bp that it should consider a particular blog/subdomain as the one it should operate on. That is defined by the BP_ROOT_BLOG in bp-core.php. Change that to the blog id that you want bp to consider it’s own. In bp-custom.php:
define( ‘BP_ROOT_BLOG’, X );
Where X is the blog id of your subdomain.
I’m not sure what you mean by ‘buddypress installed in a subdomain’. There are VPS defined ‘subdomains’ done at the server level and there are wpmu’s concept of multiple blogs as wildcard ‘subdomains’ mapping to a particular blog id.
bp is installed wherever wpmu is installed. It has no independent relationship to domains. bp only has knowledge of blog ids.
This is because BuddyPress currently runs only on WPMU, not the single-user version of WordPress
Has bp been fixed to work in subdomains yet?
When it is fixed, how do I find out?
Matt-
Have you looked at the Trent’s detailed instructions here? His instructions work with bbPress RC1.
Also, is you’re not using BP v1.0.1, it may be a good idea to upgrade.
Okay I just tried that same code on the buddypress test site and it didnt work when i tried to make my on page on my blog with that code, it just gets cleared out everytime i publish or update it.
This plugin will give to buddypress a lot of benefits,. so Nicole thanks for yor hard job…
