BuddyPress.org

thanks for the workaround DJPaul.

One question: All the fresh buddypress installation are affected with this bug ?

I am still searching why the add_filter is ignore. This is very strange.

So we should all be enormously grateful for that. I don’t think threats to move another platform are really productive.

I am grateful and Buddypress developers wouldn’t care whether I move to another platform or not. I was responding to John James Jacoby’s argument that people stick with WordPress because it has found the right balance.

WordPress is evolving from blog software to a social networking platform with Buddypress. That puts the user at the center, which is a fundamental shift in focus. That’s why I keep hammering on member management and registration.

I love the extensibility of WordPress/Buddypress, but if the foundation – member management – is a mess, that is a real problem that can force people to consider other options. I have not found good alternatives. Anahita Social Engine on Joomla could be one to watch.

Short answer: theme error is complicated. I’m writing up a Trac ticket and will put the link here later.

Workaround: duplicate your /bp-member/* folders into /wp-content/themes/. This will populate the correct info in the drop-down box. Once this issue is fixed, you can remove the duplicates from /wp-content/themes/.

I was thinking that maybe the BP Devs should change BP so that the BuddyPress themes can optionally be installed in the standard themes directory.

That way if they were able to be configured like wordpress child themes, site designers would have the option of making their BP member themes reuse styles from the theme they select for their BP home theme. That would limit the amount of CSS that needs to be developed.

I gave it a try by attempting to create a child theme of bphome. Whilst I can select it, BP ignores it and just displays bpmember.

What do you think of this suggestion?

The deep integration method I include with my BuddyBar for bbPress should take care of the 404 situation. Give it a shot and let me know how you think it works. I’m not super pro at understanding the ins and outs of SEO and redirect but I think it’s working okay so far.

From what I’m seeing in other posts, 2.8.1 isn’t quite compatible with BP yet. Keep an eye on this topic for updates.

Ok! I’m totally stuck and I have no idea why. I am trying to integrate wordpress mu 2.7.1 with the bbpress 1.01 and the most recent version of buddypress using deep integration.

As soon as I add the deep integration code:

if ( !defined( ‘ABSPATH’ ) & !defined( ‘XMLRPC_REQUEST’ )) {

define( ‘WP_USE_THEMES’, false );

//

// You will need to get the ABSOLUTE path to this file |

// \|/

include_once( ‘/home/admin/wpmu/wp-blog-header.php’ );

header( “HTTP/1.1 200 OK” );

header( “Status: 200 All rosy” );

}

I am redirected to http://wpmu.zyrot.com/wp-signup.php?new=forums.zyrot.com I can’t even install or activate the plugin. Somebody please help me here. i would really appreciate it!

Thanks

Yep, Obuisson1976 is correct. It is as if the add_filter call is ignored.

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.

I have the same trouble with the bp theme selection. The filter for “theme_root” seems to be override somewhere.

I still search why.

Hmmm…sanitizes the html…Here’s some links to the images:

Activation error

Theme error

PS. I did the whole process of a clean install exactly to the tee with WPMU 2.7.1 and it activates instantly with all themes showing correctly. So it is definitely something with WPMU 2.8.1. I don’t follow the version changes enough to know where the problem could be between 2.7.1 and 2.8.1.

Exact same problem as Agentmaximus.

Super clean install, only wpmu 2.8.1 and bp 1.0.2, nothing else.

chmod are correct as well. Upon activating I get this error:

<img src=”http://ywamheidebeek.org/temp/error-1.jpg&#8221; alt=”Activation error image” />

In the bp General Settings no bp member themes are available:

<img src=”http://ywamheidebeek.org/temp/error-2.jpg&#8221; alt=”Theme error” />

I’m glad I did not upgrade, but first tried a localhost install.

Any ideas?

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

Any update on this and can you place it when fixed in wordpress.org Plugins Directory ,so that we can download it?

I give up. I will wait until precise instructions are available for integration with bbpress 1.0.1. I’ll be closely watching this and other threads on wp mu 2.8.1. I’m not sure if it is php 5.3.0 that might be causing me problems.

I’ve tried that as well. I’m using firefox and it has a function for selecting and deleting individual cookies. I’ve also tried moving the constants to the bottom of wp-config.php since I wondered if wp-settings.php which is loaded at the bottom of wp-config.php is somehow overriding the constants.

Does bbPress actually load wp-config.php for integration to pick up settings??? I haven’t had a chance to trace through and find out what files are loaded.

John, I tried commenting out that setting and there was no joy. I’ve been focusing on the cookie domain:

on the wordpress side, on logging in the wordpress_logged_in_* cookie has the cookie *Domain* ‘.bz.dev‘, whereas on the bbpress side the cookie has the *Host* ‘bz.dev‘.

So on the wordpress side there is an extra ‘.’.

It does this irrespective of whether COOKIE_DOMAIN in wp-config.php is:

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

or

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

My understanding is that if cookie handling is the same on the wordpress and the bbpress sides of the integration, then the login state should be retained.

It seems to me that the problem is may be related to this COOKIE_DOMAIN constant and how it is being handled (or ignored) by wordpress (and/or bbpress).

@anointed check your permission and be sure that the dir owner is not root

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.