Nobody the same problem ?
Hah! I finally found what was wrong!
It’s not possible to use a secondary blog as the “material/theme” for Buddypress. At least not for the forums. It has to be the primary blog (that has incorporated BP).
Changing which blog that is this on bb-config.php doesn’t help.
$bb->wordpress_mu_primary_blog_id = 2;
Well, now I at least know why I had my problems.
Thank you for your help. I know what I did wrong : I use this plugin http://spedr.com/42utn
and used it to update the plugins as I usually do with wordpress blogs, forgetting that buddypress is also a plugin 
So I made a new install instead of trying to correct the problems.
I suggest contacting the developers of the 3rd-party plugin WishList Member and ask if and when they plan to support BP v1.1.1. Provide them with the issues you are experiencing. Since it is a paid-for plugin, and not an open source, freely available plugin, they should provide the assistance. I won’t even go into the issue of possible GPL license infringement–besides mentioning it.
Also, I’m not sure why you want to use that plugin as its purpose is to turn a WordPress-powered site into a membership-driven site. This is what BuddyPress does and a whole lot more. Better yet, BuddyPress is free!
I’m also moving this thread to “Third Party Components & Plugins” as it is does not pertain to BuddyPress but a conflict with a 3rd-party plugin.
First, if you are creating sub domains for each individual blog make sure the blogs are being confirmed through the submitted email during registration. you will see a white screen for every blog not confirmed.
If you are setting up WPMU with subdomain blogs then you have to add a wildcard DNS record on your server. If you do not, you’ll have significant issues. This is detailed in the readme.txt file that comes with the WPMU install package.
This is why we ask everyone having issues with BP if they fully tested WPMU and made sure it was functioning properly before installing ANY plugins–including BuddyPress. Fully testing does not mean giving it a cursory once over. It means fully testing all the major functions. This should take some time. The most obvious first function to test is the creation of additional blogs.
@Bolonki, I’m going to play devils advocate for a second and probably take the wrong side of this conversation, but the problem with query reduction in a social networking platform is that the only way to do it is to limit the available run-time data, or rearrange data structures to the point where other plugins can’t tap into them or repurpose them.
BuddyPress itself is a core set of 9 plugins, an abstraction layer for WPMU blogs, an API for bbPress, and comes with an elaborate set of functions and API to retrieve that data and use it in a theme; and most of this is accessible on almost every page of your website. If you need the functionality that BuddyPress provides, then hopefully you’re prepared for the overhead it takes to have all of those resources available. If you don’t need parts of it, you can turn them off and reduce queries.
This isn’t to say that BuddyPress doesn’t strive to be efficient, and in future versions you can bet that as more people become actively involved in the project that it will only get better.
Everyone has parts of web development that they’re passionate about. Some people dig SEO, some love web standards, others are worried about queries, and others are worried about server speed. There’s a lot of roles and lots of talent paying attention to all of the different aspects of what makes this all work. Remember that this is an open project, and we welcome you or anyone else to take a look at ways to make the platform better and are genuinely excited for anyone to contribute in any way.
I’m curious how many queries other social network sites use on a single page load. Can you imagine how many servers Facebook must use? Or wordpress.com? Must be pretty intense to manage all that data and traffic.
This post is two months old.
That aside. I know a couple of guys on IRC have been tracking a few SQL number-of-query issues down which apparently need to be fixed in the WordPress core. Your post is not very constructive as you haven’t suggested a particular page on a site which interested developers could look into – saying that the entire thing needs attention may be valid, but we need to start from somewhere.
Not only you Reboot, but the entire Buddypress team should be “worried about too many db queries”. Jacoby says that “WordPress has never been light”, I wonder what he thinks of Buddypress, since WPMU creates a page in about 28 queries and Buddypress needs 130 queries per page, about FOUR TIMES as many. It’s completely excessive and makes Buddypress unusable for anybody with any serious traffic and a low hosting budget. Performance (not features) should be the priority now, and the number of queries should be shown along with page generation time on testbp.org so that potential users see the kind of computing power they will need.
A few things to consider when seeing….(white screen)
First, if you are creating sub domains for each individual blog make sure the blogs are being confirmed through the submitted email during registration. you will see a white screen for every blog not confirmed.
Second, make sure all permissions are enabled in your dashboard, this too causes white screens for different blogs.
Third, make sure you deleted the bp themes in from the /mu-content/ root and that they are installed through the /mu-plugins/ not /plugins/
Fourth, a lot bp plugins take some sort of config to work correctly, sucks I know but true so I would definitely follow DJ Puals advice and deactivate all plugins while you try my suggestions.
You might be thinking that it’s a lot more difficult than that but Sometimes it’s as simple as that.
thanks DJPaul.
FYI: After reading http://www.studiograsshopper.ch/web-development/multilingual-wordpress-setting-up-wordpress/ I realized that the basic setting in wp-config could be changed (from define (‘WPLANG’, ”); to define (‘WPLANG’, ‘es_ES’); which -I think- adds Spanish (and not replaces the main language?) support.
Not sure if this setting does anything as the admin of the main blog could already choose es_ES in his blog settings (so ALL users see the blog in Spanish instead of all in English) before I ‘added’ Spanish in wp-config. (As long as the language file was uploaded to /languages of course).
Anyway, it does not change anything
– The home/community page/main blog and the buddy bar are still in the language the admin has chosen for it, not the language of the logged-in user (or a logged-out/new user for that matter).
@wordpressfan did you wrap <? ?> around it? 
@andy that still doesn’t seem to work. <?php echo xprofile_get_field_data($2); ?> gives an error. <?php echo xprofile_get_field_data($name); ?> too. 
@David
Thanks. I hope you’re right. I’m designing a site that will integrate BP functionality throughout in widget areas and the BP pages. Once I get used to using hooks in WP through functions.php, it should be OK.
Also have to learn some advanced CSS to make it all sing.
@wordpressfan. My theme probably won’t be much use to anybody else, but I think the plugins I have to build will be helpful extensions of WP/BP. I actually started designodyssey.org to chronicle what I’m learning as I build the site I’m primarily working on.
I believe GigaOM is using only extended profiles for BP:
http://pro.gigaom.com/
They’re probably haven’t upgraded to BP 1.1, since it’s a highly-customized WPMU/BP site.
—
There’s probably no “gotchas” since you’re turning everything off!
Alkivia is an alternative for user profiles:
wordpress.org/extend/plugins/alkivia/
The header is created out of simple
statements; check out the header.php for details. You can also read the codes.wordpress.org for examples on how to automatically add categories/pages to your menu.
This is just an opinion from someone who’s never used the plugin… but it’s basically for login / registration ease.
You don’t have to register a new account to become a member of someone’s BP network… just login with your Facebook account!
According to the plugin’s description, there are plans to integrate the friend list and also newsfeed publishing.
You might want to head on over to the WordPress MU forums as it sounds more like a WPMU problem:
https://mu.wordpress.org/forums/
You can login with the same username and password you use here to post on the WPMU forums!
@mark, make sure you upgrade your FeedWordpress plugin as I’m guessing you upgraded from WPMU 2.7.1 to 2.8.4a.
FeedWordPress has undergone major changes since then to be compatible with 2.8+.
Oh! and also overwrite the default WordPress RSS library with FWP’s Magpie RSS library.
For more, read the upgrade installation instructions:
https://wordpress.org/extend/plugins/feedwordpress/installation/
Argggg, I spent 24 hours of non-stop trial and error (considering I am a PHP noob) to make my site work after the buddypress 1.1.1 upgrade. Made a lot of tweaking with the avenuek9 theme to look like how my site used to looked like before the upgrade. I hope you gurus can make this How-to- stuff soon. If you look at my site, its still a mess (http://bloggista.net) but it should be back in its handsome form once those minor issues are ironed out. Like, the recently active avatars are lining up in single file down to the bottom as if they’re queuing for the some firing squad.
Thanks folks, looking forward to it.
Hi snagfly. I’m the author of that plugin. It sounds like the problem is that you activated the bbPress trigger plugin inside of WordPress. As is stated in the readme files, this part of the plugin is only needed if you are running a separate installation of bbPress with BuddyPress 1.0.
If you are running BuddyPress 1.1+, you can safely delete the file bb-group-forum-subscription.php, keeping and activating only bp-group-forum-subscription.php.
I would prefer moving all admin for members out of wp-admin into the site, instead of trying to make wp-admin look more like the site. Keep wp-admin for admin only and put all member functionality in the site.
That’s not a bad idea… just making an admin theme that looks more consistent with BuddyPress. Less jarring for newbies.
Previous to BP 1.1, all user registration was dealt with by WordPress, so it’s technically correct to point people towards existing WordPress/MU resources and forums for help.
Since BP 1.1, however, BP changes the new account confirmation/activation email – because on the standard BP 1.1 signup page, the user can pick their own password. And of course, it’s a security issue if we were to somehow send their (encrypted) password back to them. So BP 1.1 overrides the standard WordPress MU email so it doesn’t include the password text.
But, the activation link is part of WordPress. Yes, the BuddyPress default theme uses this behaviour too – but it calls the WordPress code.
Yes it is confusing for users that you have to make a post to one place and to change your avatar to another.
Well what we are doing now, is putting all buddypress ‘admin’ settings in the wp-admin and reorganized them…
right now we have:
Posts
Comments
Messages
Settings
Appearance
(with submenus off course)
Everything else is stripped out. I can imagine 100 of structuring this, but for this particular install, this is what we needed.
We have very limited time.
So what i did is used an existing “admin theme plugin” and changed it so the wp-admin matches the look and feel of our front end. (think eg. facebook ‘front and back’, or lastfm etc ).
The most difficult part is getting the bp functionality such as messages completely work back end. Which atm we haven’t managed yet.
I’m still lost. I also don’t really have time to look at this until the weekend sometime. Could you help me again please?
Yep, I go to the main blog via Users menu (not site admin>users) and…
Could you give me a sample link (feel free to cut your domain off the beginning), i.e. http://example.com/how_to/get_to_this/page. I’m being a noob and can’t see it
...EXCEPT the email with username & randomly generated password that should replace that activation email shown above. (I'm thinking this is a wordpress email? Not sure.)
Correct. Welcome Pack doesn’t (or shouldn’t) touch the activation email, which is why this issue is so weird-sounding.
You ARE aware since BP 1.1, if a new user registers via http://testbp.org/register, they are able to pick their password and as such it isn’t emailed to them? (Though they still get a confirmation/account activation email)
@jeff
I appreciate the feedback and perspective. What’s weird is I built a modular php/mysql site circa 2002 basically overusing includes, very basic css and taking functionality from Hotscripts.com’s PHP repository. In fact, what I liked about php was the modularity of what I was doing (even if a bit sloppy). BP/Wordpress seems to promise the same, but frankly the number of sites that deviate from the structure of the standard theme is small (maybe it’s too new). It’s like the complexity of the theme structure has scared people off or the fact that the themes are both style and functionality makes it difficult to be modular.
I’m hard-headed and have no hurried timeline – I’m designing for myself. I’ll probably take this on and suffer the pain of BP’s infancy just like I did in 2002. That was my education. What would be helpful is a methodology for taking on something like this.
My threshhold question is whether to use a theme framework as a starting point or whether that’ll be too restrictive and I just need to bite the bullet and build my own theme. I’d be on the hook for updates (sucks), but it sounds like it may save some pain. My limited understanding of actions/filters is that I should be able to build almost anything from a good theme framework using functions.php and style.css, etc., but not sure if that’s true or whether it’s worth pain of learning that way of developing instead of just tearing apart templates.
I’m sure, by the time I’m done there’ll be dozens of modular BP themes/frameworks to choose from. That’s what happened after I slaved over the site in 2002. Who knew WP was there with plugins for most of the stuff I hardcoded myself.
