Forum Replies Created
-
In reply to: News doesn’t work in blogs
The ‘news’ button only works if the home theme is running on blog id 1. Sounds like it isn’t. You have to hack some stuff to get it to work. If you are comfortable changing the code in the home theme then it’s here:
if ( $current_blog->blog_id > 1 )
return false;lines 59/50 in themes/buddypress-home/functions.php. Comment those out and news works.
In reply to: Group forums working yet not workingI’m glad you found what you were looking for Mike. I’ve never worked with mu either. Matter of fact I’ve been out of the biz for 8 yrs. Just got back to the fun about 4/5 months ago.
You’ll likely be hearing form me again.
Ha. Speak up then. I’m usually too busy being loud to hear what others are saying.
In reply to: Group forums working yet not workingHowdy 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.
In reply to: bbPress Integrationwpmu/bp and bbpress exist together side-by-side. wpmu/bp doesn’t have a forum. Well, it does: bbpress.
In reply to: Group forums working yet not working@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?)
In reply to: Group forums working yet not workingAndy, 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.
In reply to: Group forums working yet not workingThis 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” } }
In reply to: Group forums working yet not workingwp_remote_get() is a new function to 2.7 it lives in wp-includes/http.php
Looks like the http.php file is new to 2.7. Problems there in some instances?
In reply to: Group forums working yet not workingThings go south at wp_remote_get() inside /wp-includes/comment.php discover_pingback_uri()
In reply to: Group forums working yet not workingThis is why I’m looking at the environment the code is running in and not the code anymore. Same code on windows dev server as live server. Same .htaccess files. Essentially the same httpd.conf files for apache.
Gonna go look for small animals to hurt soon.
In reply to: Group forums working yet not workingWhen 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.
In reply to: Group forums working yet not workingAnd 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.
In reply to: Group forums working yet not workingHi Andy, here ya go:
bool(false) object(IXR_Error)#292 (2) { [“code”]=> int(-32300) [“message”]=> string(114) “transport error – could not open socket: 0 php_network_getaddresses: getaddrinfo failed: Name or service not known” }
In reply to: Group forums working yet not workingI 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
In reply to: Group forums working yet not workingI’m off to try this again. The SVN logs show that the bbpress guys have been busy.
In reply to: members link and admin link on home page dont workIt’s difficult to help you because I can’t simulate your installation. You have wpmu configured to use subdirectories and I have it setup to use subdomains.
In reply to: members link and admin link on home page dont workI went to your site and I see what it is doing. I have no idea why though. I did notice that you’ve installed mu with the subdirectory option and you are running the bp home theme on your ‘sajjadkhan’ blog. I don’t know what that would have to do with it but try selecting a different theme for your other blog.
The error msg looks like you have the bp home theme in /wp-content/member-themes
Got me.
In reply to: Group forums working yet not working@wardeh, bearuser
I’m having the same problems. The forums aren’t getting created because bp tries to go verify and get an url to use from bbpress. bbpress is reporting 404 for me when bp (actually mu) tries to get that url from bbpress. It’s the url in group forums admin screen.
On a dev machine I’ve got running everything works fine. On the live server it doesn’t because of that. Still trying to debug it. If anyone wants to lend a different perspective the failure is in:
function discover_pingback_server_uri($url, $deprecated = 2048) {
$pingback_str_dquote = 'rel="pingback"';
$pingback_str_squote = 'rel='pingback'';
/** @todo Should use Filter Extension or custom preg_match instead. */
$parsed_url = parse_url($url);
if ( ! isset( $parsed_url ) ) // Not an URL. This should never happen.
return false;
$response = wp_remote_get( $url, array( 'timeout' => 2, 'httpversion' => '1.1' ) );
if ( is_wp_error( $response ) )
return false;
if ( isset( $response ) )
return $response;
// Not an (x)html, sgml, or xml page, no use going further.
if ( isset( $response ) && preg_match('#(image|audio|video|model)/#is', $response) )
return false;
$contents = $response;
[snip] and other junk beyond that…
That lives in /wp-includes/comment.php
The param $url is fine. It’s what is in the group forums admin screen. The point of failure is when it gets a $response back from wp_remote_get(). It gets 404. So functions higher up the food chain that eventually call this think that there isn’t a ‘pingback server uri’. So nothing happens. No forum creation. No forum, no topics. No nothing.
That’s as far as I’ve gotten with this. Usually explaining it makes it clearer but not this time. Gotta go delve into bbpress and see why it’s returning 404 for a simple ‘gimme the header and your html for the url where you live’.
In reply to: Group forums working yet not workingwardeh and others,
there is a little link to an .htaccess file you need to put in the bbpress directory. In bbpress settings > general settings > pretty permalink types you’ll see a notice that you need to create a .htaccess file with a link to ‘privided here’. Cut and paste, send it up to your bbpress root directory.
bbpress needs a .htaccess file for apache if you are running permalinks and not the xxx.php?something type of url.
@punkky Well, I think you’ll still need to go in the existing blogs and make them public. The ‘privateness’ of your blogs is determined, from bp’s perspective in this particular case, by the Settings > Privacy toggle. I think, if I remember correctly, if this is Friday. That would be the only place.
I gotta go fix my group forums. I’m just avoiding the issue by talking on the forums. If I play around in the forums long enough my site will see the error of it’s ways and fix itself right?
In reply to: /members/ going to blank pagesThe condition you describe is a common one for programmers and other geeky type tech people. We are so self-centered that what we do is *always* right and it never occurs to us that no, the source of the problem might be me.
“Can’t be *my* code…”
Then there is my favorite way of dealing with problems. Stare at them until they go away. Hasn’t worked yet but I have high hopes for that one.
What should also be included in this list of ways *not* to solve problems is devloping a raging case of code blindness. The primary symptom is ignoring the obvious. When I was working as a corporate programmer weasel I’d stare at the same piece of code for days and not see the problem it was causing. A co-worker would hear the quiet sobbing in my cubicle and come over to console me and just glance at the code and point out the error of my ways. Smirking and gloating he walks away with a new swing in his stride.
Ya look so stupid until he develops it next week. What goes around comes around. Smirking and gloating I walk away with a new swing in my stride.
In reply to: members link and admin link on home page dont workIt doesn’t look like you have things configured quite right yet.
The bp home theme shouldn’t be in: /wp-content/member-themes it should be in: /wp-content/themes
The bp member theme should be in: /wp-content/member-themes
What is confusing to me is that it’s reporting an error looking for *anything* in /wp-content/member-themes/buddypress-home/. That directory path doesn’t exist. Shouldn’t exist.
In reply to: /members/ going to blank pagesThose errors are normal. Normal? Well, everybody has them for the moment. Nothing to get excited about. The URLs for the menu items you are having problems with are launching stuff in the member theme.
Double check the member theme installation. Should be in /wp-content/member-themes/(stuff here)
Any custom code in your bp install?
In reply to: Removing Blog Links in profiles…Don’t install the blogs component and those things go away automagicly. A quick way to do this if you already have it installed is to rename /wp-content/mu-plugins/bp-blogs.php to /wp-content/mu-plugins/bp-blogs.php.OFF
In reply to: /members/ going to blank pagesIs wpmu 2.7 out now? Your site says its running “WordPress 2.7” not “WordPress 2.7-RC1-xxxx” like everyone else. The site in your profile must not be the site you are talking about.
Anyway, the dreaded “white screen of death” probably means you have some errors and it’s just not showing you them. Check your php and apache error logs and report back.
Sounds like the bp member theme is crashing for some reason. Do you have *all* the bp components installed?