BuddyPress.org

Howdy mike,

1. Yup. bp relies on bbpress for it’s forums.

2. ahhh… you can’t not have one. It’s the only way that mu knows where to go for your database and other such things. You looking in the correct dir?

3. Torturing animals is high-level?

Until somebody chimes in with a magic solution to all this, I’m gonna go work on a theme. So there.

@meerblickzimmer What is the difference between the two installs on the same server?

Is one wpmu/bbpress using user integration and the other not? What’s the difference?

If we know the diff then maybe we can narrow down the problem.

ASIDE: Yes, curl is turned on on my live server. (is that english?)

Andy, this is the results from WP_Http obj in http.php. It’s using cURL to go get the info from bbpress. Below are var dumps from line 261 in http.php

‘http obj url param:’ = $url

‘http obj request param:’ = $r

… you get the idea …

http obj url param: string(37) “http://ourcommoninterest.org/bbpress/”

http obj request param: array( { [“method”]=> string(3) “GET” [“timeout”]=> int(2) [“redirection”]=> int(5) [“httpversion”]=> string(3) “1.1” [“user-agent”]=> string(13) “WordPress/2.7” [“blocking”]=> bool(true) [“headers”]=> array(0) { } [“body”]=> NULL }

http obj transport: object(WP_Http_Curl)#324 (0) { }

http obj response: array(3) { [“headers”]=> array(5) { [“date”]=> string(29) “Sun, 14 Dec 2008 01:52:04 GMT” [“server”]=> string(21) “Apache/2.2.3 (CentOS)” [“content-length”]=> string(3) “292” [“connection”]=> string(5) “close” [“content-type”]=> string(29) “text/html; charset=iso-8859-1” } [“body”]=> string(292) “

Not Found

The requested URL /bbpress/ was not found on this server.

Apache/2.2.3 (CentOS) Server at ourcommoninterest.org Port 80

” [“response”]=> array(2) { [“code”]=> int(404) [“message”]=> string(9) “Not Found” } }

I know that curl is fired up on my windows server. Can’t imagine it isn’t on my linux server. Besides, the http obj tests all ‘transports’ for their existence before sticking ’em in the list of those to try at that spot where the dump is. Gonna go look anyway.

Since this code is new in mu 2.7 I don’t trust it.

This is the var_dump of $response in discover_pingback_uri()

at pingback discover : array(3) { [“headers”]=> array(5) { [“date”]=> string(29) “Sat, 13 Dec 2008 21:35:35 GMT” [“server”]=> string(21) “Apache/2.2.3 (CentOS)” [“content-length”]=> string(3) “292” [“connection”]=> string(5) “close” [“content-type”]=> string(29) “text/html; charset=iso-8859-1” } [“body”]=> string(292) “

Not Found

The requested URL /bbpress/ was not found on this server.

Apache/2.2.3 (CentOS) Server at ourcommoninterest.org Port 80

” [“response”]=> array(2) { [“code”]=> int(404) [“message”]=> string(9) “Not Found” } }

When bbpress_Live_Fetch obj’s constructor is called it calls $this->set_endpoint(). If it can’t get a valid endpoint then query is gonna always fail. set_endpoint() calls discover_pingback_server_uri() and it fails inside there with 404.

And also $this->options

array(4) { [“target_uri”]=> string(37) “http://ourcommoninterest.org/bbpress/” [“username”]=> string(4) “bpbb” [“password”]=> string(6) “xxx” [“always_use_auth”]=> bool(false) }

no the password is not ‘xxx’ and yes it is correct.

I think that what we are experiencing here is an apache phenomenon.

We can’t all be setting this up improperly. Besides, I’ve got it working on a windows dev server just fine. It’s running the same vers of all 3 software components. bp, bb, mu. Same.

I’m telling you people that when I dig down in the bowels of the code the reason that things are failing is wp_remote_get(‘your_very_own_url_to_bbpress’). It’s returning 404 and nothing happens after that. Well, things happen happily along as usual but everything above that just can’t work without that ‘pingback uri’ that it is looking for.

So why is a valid url for the bbpress root returning 404? Apache and it’s wonderful .htaccess files control that response. If following it’s internal .htaccess rules that exist in the mu root and the bbpress root, if it decides that what you are requesting doesn’t exist, then it just plain doesn’t. To apache. Returns 404.

I don’t know how anyone else has bbpress installed but mine is like so:

mu root = myhappydomain.org/

bbpress root = myhappydomain.org/bbpress/

The .htaccess conditions and rules in mu dir get processed first. Then the ones in the bbpress dir get looked at.

HANGON: gotta run go do something but i’m hitting ‘save’ first. brb

I’m off to try this again. The SVN logs show that the bbpress guys have been busy.