That didnt work…I really have done nothing to the code the only thing I have modified is the css to make it look different. The only bp addons are the flickr and youtube plugins.
Wp plugins are share this and thats it. This did not work from the first time I installed buddypress so it could not have been something I did.
http://teamjaren.no – its a cycle-club.
I found the bp_login_bar() in the file /bp-core/bp-core-templatetags.php on line 489. You could just edit this directly or add an optional parameter to this function.
Maybe this could be added as a feature of BuddyPress?
In the mu-plugins folder you find the buddypress activity plugin.
It has a subfolder called feeds.
Al three of them use
header(‘status: 200 OK’);
But it should be
header(‘http/1.1 200 OK);
It worked for me 
Yes, when I click on a link in an email to accept a friend, I get the “Are you sure you want to do this?” message. The link in the email looks like this:
Accept the friendship request:
https://blogs.example.com/members/auser/friends/requests/accept/22?_wpnonce=8b608e4a0d
nicola has tinyMCE running on his site. I don’t remember if he has that as just a part of the theme or if it’s a plugin. Works great. Check it out at:
http://buddypressdev.org/
It actually doesn’t matter if you do it during installation or after… it turns out to be the same.
Have you seen this article:
http://bavatuesdays.com/integrating-wpmu-buddypress-and-bbpress/
It was extremely helpful with my setup and includes the video you mentioned, with some additional pointers. Also read the comment section for some addtional info.
Just make sure you have the latest versions of both and start off fresh. Follow the article I quoted and give that sigh of relief when you switch from WordPress MU to bbpress and see “Welcome admin!” on top instead of “Login”….
My admin_bar at admin wordpress mu dashboard doesn’t translated, only de admin bar at buddypress area is translated.
Can you post this on trac so I remember to check it?
https://trac.buddypress.org/newticket (same login)
Where specifically, on which user actions? If it’s links in emails then this is a known issue, it’ll be fixed soon.
@awarner20 your problem with the email friendship requests is a bug. Can’t be solved with a one liner. Sorry. I did submit a workaround patch in trac though:
https://trac.buddypress.org/ticket/519
It eliminates the problem by eliminating the problem. Lemme explain. When a user requests friendship an email is sent out to the destination user. The destination user is supposed to click the link and it automatically approves or rejects the request. Doesn’t work due to the fact that a security mechanism is being used to validate the process. The ‘nonce’ security scheme uses the originating user’s identity and some other stuff to come up with this ‘nonce’ key. The key is only valid when used by the originating user.
When the destination user clicks on the link the key is used but they are not the originating user. So the security check fails. Andy is aware of the problem. I just removed the automatic accept/reject links and used a link to the destination user’s friendship notifications page where it will have to be manually accepted or rejected.
Andy, I’m running the latest default themes from SVN but still having the _wpnonce error.
Josswin: you need to upgrade the themes, or read the second post on this thread – the bit about _wpnonce.
Hi Fishbowl81,
I want to make the bbpress forum to load in my buddypress site from a tab ‘forum’ which is like other tabs like home, blog, members. As you have on your site gorgeousgamers.com.
So that it incorporates the sites design theme and can still navigate through other tabs.
What is the best way around this?
Many thanks,
“Whenever I click on a link to accept a friendship request…” should read:
“Whenever I click on a link IN AN EMAIL to accept a friendship request…”
I’m running the latest version of SVN trunk, using the default home and members themes. Whenever I click on a link to accept a friendship request, I get the “Are you sure you want to do this?” message. Any suggestions? Thank you.
I might add this is also happening on my test installation, too, running the same setup, only in a sub dir.
egerrits are you working too on that?
I’ve almost finished mine
Add it here http://buddypressdev.org/add-plugin
egerrits, If you need help for that posting twitter issue, liaison with this developer
http://www.phpvrouwen.nl/2009/01/04/twitme-17-on-buddypress/
./wordpress-mu-root-dirctory/whatever-you-want
Mine is at delsolownersclub.com/discussions/
You just need to make sure you reference that directory everyplace you need to within BuddyPress and bbPress to make sure they see each other.
SWEEET SUCCESSSSS!
Okay… For those of that might be using “deep integration” namely using your BuddyPress/MU functions in bbPress, at the time of this writing at the top of your bb-config.php file, put…
if ( !defined( 'ABSPATH' ) & !defined('XMLRPC_REQUEST')) {
include_once( 'absolute/path/to/your/wordpressmu-directory/wp-blog-header.php' );
}
This way, it only tries to include the MU/BP functions if they haven’t already been defined and if it’s NOT a xmlrpc request!
DUH! Yay! Burt, haha you rule…
Found the problem with the 404 page showing up on a redirect with buddypress. It’s not buddypress.
in wp-includes/pluggable.php in the main wp core the function wp_redirect –
if ( $is_IIS ) {
header(“Refresh: 0;url=$location”);
} else {
if ( php_sapi_name() != ‘cgi-fcgi’ )
status_header($status); // This causes problems on IIS and some FastCGI setups
header(“Location: $location”);
}
the $is_IIS is doing a REFRESH: 0; url=location when on windows server 2008 header(“Location: $location”); works fine with the latest fast-cgi module release
SOO basically in wp-includes vars.php making this change:
/**
* Whether the server software is IIS or something else
* @global bool $is_IIS
*/
if (strpos($_SERVER, ‘Microsoft-IIS’)) {
if (strpos($_SERVER, ‘Microsoft-IIS/7.0’)) {
$is_IIS = false;
} else {
$is_IIS = true; // (strpos($_SERVER, ‘Microsoft-IIS’) !== false) ? true : false;
}
} else {
$is_IIS = false;
}
fixed it, by declaring that a microsoft-iis/7.0 server is *not* iis
