BuddyPress.org

There is a very delicate balance here because on one hand all of the developers leveraging [Word/Buddy/BB]Press are getting an enormous head start compared to building something from scratch. So we should all be enormously grateful for that. I don’t think threats to move another platform are really productive.

At the same time, critical feedback and vigorous debate will make the product better. I don’t think this should be characterized as moaning. Active threads on the membership architecture would be great to see (I know Peter has tried to start a couple of those).

Most people here would agree with Peter that the WPMU+BP membership functionality is not ideal. They would probably also agree that Andy’s compromise is a good one under the constraints of WPMU. BuddyPress will be a good forcing function to make that improve though.

Adopting some strict framework is not the answer. The trash heap is piled high with projects that had high architectural ideals. The successful stuff delivers a good user experience, often with frightening hacks under the covers, but over time becoming more robust and beautiful inside too.

There is a key architectural aspect to *Press that makes it successful though – extensibility. The hooks make it possible to hack the system to do so many things that weren’t even considered when the projects were originally conceived. Andy has exploited the extensibility in WPMU to bend it into a social networking system. He has also been religious about putting hooks everywhere to give us the same opportunity with the things we in turn build on top of BP.

As long as we are all being creative on *Press, things won’t be pure. Andy will be bending WPMU to his will and we will be bending BP to our will. That’s the beauty of it.

There is a bug with running the latest version of WordPress MU and BuddyPress together. I am not aware of a proper fix yet, keep your eye on https://buddypress.org/forums/topic/wordpress-mu-281-released.

There seems to be an issue with bp-themes in the wp-content/bp-themes directory. There does not appear to be anywhere to activate theme.

According to instructions in the readme, BuddyPress themes (other than the default ‘bpmember’ theme need to be activated before they are used).

Based on the instructions in the readme in the bp-themes directory I looked for a menu “Site Admin -> BuddyPress”. This menu doesn’t exist (although this is the menu that the instructions say is needed to activate Buddypress Themes).

I then went to the “BuddyPress -> General Settings Menu”. This has a dropdown list “Select theme to use for BuddyPress generated pages”. This dropdown is listing the wordpress themes and not the buddypress themes like bpskeleton which comes with the 1.02 download. There is nowhere I can find to activate the BuddyPress themes so that they appear in this list. In the dropdown above, I tried selecting one of the themes listed e.g. “wordpress mu homepage”. Once I apply it and go to the buddyPress-generated pages like “/members”, “/groups” or “/blogs” I see this message:

You do not have any BuddyPress themes installed.

Please move “/wp-content/plugins/buddypress/bp-themes/” to “/wp-content/bp-themes/” and refresh this page. You can download more themes here.

Note:

My installation is a clean install from wpmu 2.8.1 with buddypress 1.0.2

Is anyone having any success determining the steps for a fresh install of WP MU 2.8.1, bbPress 1.0.1 and buddypress 1.0.2?

I can’t get the WP MU 2.8.1 and bbPress 1.0.1 integration playing together. I’ve tried the bbPress Integration plugin for wordpress. This plugin shows one section with wordpress constants COOKIEHASH, COOKIE_DOMAIN, SITECOOKIEPATH and COOKIEPATH under the “Save Changes” button:

define( ‘COOKIEHASH’, ‘8601cf66cb0dd7bfc31ae5a1499a18a4’ );

define( ‘COOKIE_DOMAIN’, ‘.bz.dev’ );

define( ‘SITECOOKIEPATH’, ‘/’ );

define( ‘COOKIEPATH’, ‘/’ );

I’m working on an offline development server on my Mac (XAMPP running php 5.3.0). I was using MAMP Pro but stopped using that when I found out their was an incompatibility with the libxml / php versions it was using.

Currently I have to logout of one backend to access (login) to the other (or clear cookies) to access either backend. I can’t be logged into both at the same time. It’s sharing usernames and password okay …

Are there any tricks that people have been using to try and debug this?

I’m quite keen to work from a fresh install of latest releases of all the components rather than working through upgrades of previous versions (which are also tricky to integrate).

I’ve tried stirring in newt’s eyes and frogs legs into the cauldron but they don’t seem to help.

well i didn’t go anywhere near the php.ini file as this is a dedicated server and I don’t separate them out on a per site basis.

the .htaccess file was not overwritten, left that intentionally.

I’m going to try it one more time and see if it helps.

I did have one problem that I forgot about. I accidentally deactivated buddypress before I deactivated all the plugins that rely upon it. That resulted in a 500 error. I had just removed the offending plugins that rely upon buddypress via ftp, figuring that would solve the problem. Which it ‘appeared’ to do, but obviously not.

So I reactivated buddypress, then reupped the other plugins via ftp, and then did the deactivation the right way. Now all are properly deactivated and I’m replacing files again.

will report back.

John: reminds me:

burt actually asked me to send you a pm regarding an ‘issue’ i am having as he is to busy with his move. I’ll send it after this final attempt.

I have had no luck at all trying to upgrade from 2.7.1 to 2.8.1

Here are the steps I am following:

1. backup all files and db – done

2. deactivate all plugins on the main blog

3. remove all plugins from the mu-plugins folder

4. delete wp-admin and wp-includes folders from server

5. upload all new 2.8.1 files to the server

Then when I try to reach any page on the server I get a 500 error which is as follows:

PHP Fatal error: Call to undefined function wp_clone() in /website.net/wp-includes/cache.php on line 380

The only thing I can do at this point is to delete all the new files I uploaded and replace them with the old 2.7.1 files…

I have tried this 4 times so far with no luck. I have made absolute certain that all the files are properly overwritten, but still end up with the error.

Is there a solution to this problem, or am I the only one with it?

I’ve read the upgrade docs, and as far as I can tell I am not missing a step, so I’m really stumped here…..

btw

my buddypress install is NOT on the primary blog, so I did not have to change the theme. It is a wp standard theme on the primary blog

@Russell:

HOWEVER…

I lose the forums function in BuddyPress groups

Remember you also need the XMLRPC call in your bb-config.php as well for group forums.

$bb->bb_xmlrpc_allow_user_switching = true;

(goes right before ?> in bb-config.php)

Do this again and make sure you have the XMLRPC line in bb-config.php

JJJ’s method, it looks like /home/public_html/…

But that way will get BuddyBar in bbPress to work and my forums integration from BuddyPress breaks.

The only way to keep the forums integration in BuddyPress is to leave it as http://mywebsite.com/wp-blog-hear.php

I just have no idea why that works…

– Understanding how these 3 pages works in general. Do they belong to the bp-member or bp-home theme or both.

They are styled in the bpmember theme, which is a BuddyPress theme.

The bphome theme is a WordPress theme.

– Figuring out how I create a copy of lets say the Member page, then give that page an entire new name/slug.

Not sure about creating interior BP pages… I know certain BP plugins create their own slug and pages (eg. bpEvents, bpContents).

But depending on what type of page you are planning on creating, I would just create a new page in WP and assign a WP page template that is setup almost identical to the bpmember component in question. This would be the easiest route if you want total control of the page.

However, before you do, you might want to consult with a mod who has more experience with BP than I do!

I followed r-a-y’s advice and used the ABS path in my bb-config.php file.

I can activate and use the BuddyBar in bbPress normally.

HOWEVER…

I lose the forums function in BuddyPress groups, but if I go back to bb-config.php and use the URL for the include_once line I get the forums functionality back and BuddyBar stops working, i.e. it disappears from bbPress.

I guess I don’t REALLY have deep integration working, but the forums functionality works as I would expect and right now that is what I am concerned about.

I’m going to have to sit out and watch this play out and hopefully an easy to follow guide comes out to integrate the latest versions of WPMU, BP, and BB.

My setup may not be “right” but it works as I want it so that’s all I can ask for right now.

Just tried this for one of our groups and you’re right. It doesn’t work. Like you, I hope this bug gets squashed since email notifications to group members is the very essence of the functionality of Buddypress.

@Indojepang

It could be an issue with rewrite rules. Read these two threads. Please not that Nginx does not (read cannot) use a .htaccess file.

https://buddypress.org/forums/topic/404-errors-using-yahoo-to-host#post-16797

https://buddypress.org/forums/topic/nginx-re-write-rules

Hey amweiss,

If you can’t wait for Jeff’s component, there is another one out in the wild by Sandra Petronic:

http://devbox.computec.de/2009/06/buddypress-xprofile-privacy-plugin/

Hope that helps!

Of course not, that wasn’t my point. The registration functionality in WPMU is quite restrictive and cumbersome right now. That will improve though. If you’re concerned about this, then don’t consider BuddyPress as we’re only on version 1.0.

I was going to take the gamble that it would improve over time. Hearing most developers here dismissing any architectural criticism and only singing the praises of WordPress is not encouraging though.

You know why people that join fraternities rarely ever leave? Because once you’ve gone through the hazing, you’re more likely to stay.

Right, once you’ve decided on a platform it’s very hard to go anywhere else. You’re stuck.

Every couple of years I reevaluate what to use for my websites. I started on Nucleus. The current version of my project Web2NewYork is built on WordPress with a members registration system based on code taken from PunBB.

I switched to WordPress reluctantly only because it was becoming the standard. I’m now trying to consolidate on Buddypress, if I can everything working before September. If member management/registration does not improve I will have to switch to something else next year.

Not at this point. Look at the BP roadmap (v1.2) and look at this.

No one can answer on Nicola’s behalf, but it sounds like he’s abandoning development on this project to me, in lieu of it being a core feature eventually.

This would work not unlike the way wordpress.com allows you to map your blog to another domain. I suspect that would basically end up being this, or vice versa? That being said, it sounds like a WPMU feature that would have a piggy back panel for BuddyPress to me.

Does that mean I have to keep my mouth shut about the crappy patched together membership management mess that will now become the foundation of my project?

Of course not, that wasn’t my point. The registration functionality in WPMU is quite restrictive and cumbersome right now. That will improve though. If you’re concerned about this, then don’t consider BuddyPress as we’re only on version 1.0.