BuddyPress.org

I’m having the same exact problem as well! Every page is Error 404. Fresh WordPress MU install followed by a fresh BuddyPress install. Error 404 on every page.

Might this have to do with htaccess? Are files missing? (I re-installed, but problem still persists)

https://wordpress.org/extend/plugins/bbpress-latest-discussion/

it works wih bp 1.1.1

@Jacoby who wrote “I’m curious how many queries other social network sites use on a single page load.”

I was too, and saw that it varies widely — from about 40 queries per page for the commercial SocialEngine script (which now includes Zend fragment and full page caching, very nice) to the mind-blowing 1.364 queries just to show the Dashboard on Elgg as reported in Elgg’s own forum. As for Drupal, it makes a similar number of queries per page as BuddyPress (of course it depends on the number of modules, etc) and with that level it is such a mess that Jesse Farmer, the main developer for Popsugar (the most trafficked social network built on Drupal) abandoned the project and wrote on a developers forum that Drupal is impossible to scale and “it would have been easier to start from scratch”. And bear in mind that Popsugar got $5 million from Sequoia Capital, so they have plenty of money to “throw hardware” at the problem.

@DJPaul, who said “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.”

I am not a coder, so how about starting here: I will pay $500 dollars to the person or team that reduces the number of queries on the main Buddypress blog page to around 20 (which is the normal number for a WordPress blog running the default theme). I am ready to escrow this money on the site of their preference.

Hey all. I have just been hired full time as a web developer and videographer for a major medical school. The idea is to create a site that will recruit more young people to go into healthcare related fields.

Anyway, I want to use WPMU and Buddypress as the architecture for content management and some social networking components. I have a good bit of WordPress experience, but am completely new to BuddyPress. I am right now in the process of developing a totally custom theme for the site.

There is a lot of content outside just the main blog and the BuddyPress components. The wordpress functionality is basically complete and I’m now starting on the BuddyPress portion. I’m a bit confused as to how to step into the theme development. Is there a good explainer somewhere that might help me understand how exactly the BP components are called or hooked into what would otherwise be a standard WP theme?

I would not be able to share the custom build with the community as it would not have any applicability outside this site, but once I get my feet wet, I would be happy to help develop a more generic theme to donate to the cause.

Personally… I would just try to make it work with jQuery instead since WordPress already includes it… and then you won’t be using two JS Frameworks. I’m pretty sure that anything MooTools can do… jQuery can do.

I was looking at http://www.dailywp.com/jobpress-wordpress-theme/ which is in use at http://jobs.smashingmagazine.com/. I was wondering if it was compatible with WPMU and Buddypress.

I would definitely interested in ur jobboard component!

I have not seen anyone on the BuddyPress forums reporting that they are using this plugin. You are the first that I’ve seen.

From the error message, it looks like WPMU has an issue with some code in the plugin. It could be caused by another plugin you’ve installed being incompatible or simply a bug within the plugin itself.

Your best bet is to contact the plugin developer, tell them about the error, and ask whether it works with BP v1.1.1.

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.