[fakeplasticfish]

Not sure if this question should go to the Installation forum or Troubleshooting. I actually posted this question last night to the forum, and this morning it has disappeared. So trying again…

I have spent all weekend installing bbPress and modifying the kakumei template to integrate with my site. It all looked great in Firefox and Safari, but when I view the site in Internet Explorer 8, I cannot reach any pages besides front page, and only then if I browse to http://fakeplasticfish.com/discuss/index.php. Simply browsing to http://fakeplasticfish.com/discuss/ in Internet Explorer brings up a 404 Error, as do all the other forum pages.

Here are details of my install:

WordPress 2.8.4 installed at the root: http://fakeplasticfish.com

bbPress 1.0.2 installed at http://fakeplasticfish.com/install/

bbPress is installed into the same database as WordPress on a GoDaddy Linux server.

I have added this code to my bb-config file as instructed:

/** Integrate with WordPress */

require_once(‘/home/content/b/e/t/bethfish/html/wp-blog-header.php’);

This is because I want my WordPress plugin menu bar to appear in bbPress as well as other WordPress functions.

I thought perhaps the issue had to do with pretty permalinks, as I read some entries in this forum on that issue, so I actually switched back to the original ugly permalinks, cleared the browser cache and restarted IE. IE will still not open any of the bbPress pages besides index.php and returns a 404 error from the server (not my WordPress 404 page.)

I have two .htaccess files, one in the root folder created by WordPress and one in /discuss/ created by bbPress. I tried deleting that file after switching back to ugly permalinks, and now there is a new one there.

I am a novice. I don’t understand the information in the .htaccess file, but I am happy to copy the information from both files over here if that would help.

I just really don’t understand why the bbPress pages work fine in Firefox and Safari and not in IE.

[chrishajer]

I think you should be including wp-load.php instead of wp-blog-header.php

I think the difference between browsers is due to your forum returning a 404 but still displaying the content. Some browsers ignore the 404 and display the content (Safari and Firefox, apparently) but others treat the 404 as a 404 (IE8).

Check the headers being returned from http://fakeplasticfish.com/discuss/ :

Date: Sun, 01 Nov 2009 20:34:48 GMT

Server: Apache

Cache-Control: no-cache, must-revalidate, max-age=0

Expires: Wed, 11 Jan 1984 05:00:00 GMT

Pragma: no-cache

X-Pingback: http://fakeplasticfish.com/xmlrpc.php

Last-Modified: Sun, 01 Nov 2009 20:34:48 GMT

Keep-Alive: timeout=15, max=98

Connection: Keep-Alive

Transfer-Encoding: chunked

Content-Type: text/html; charset=UTF-8



404

https://bbpress.org/forums/topic/deep-integration-google-might-not-be-indexing-your-forum-pages

https://bbpress.org/forums/topic/help-404-error-but-page-displays

https://bbpress.org/forums/topic/bbpress-wordpress-mu-or-not-leads-to-404-errors-but-pages-still-load

I think those are related.

[fakeplasticfish]

Oh my god, I love you. Will you have my babies???!!!!!

Changing from wp-blog-header.php to wp-load.php fixed the problem. At least it looks that way. The pages are loading in IE now.

How would I check to headers to make sure this problem is truly fixed? I don’t know what “check the headers” actually means. Sorry.

Oh, and maybe bbPress could change the instructions here

https://bbpress.org/documentation/integration-with-wordpress/

to indicate that wp-load.php should be used instead?

Beth

[chrishajer]

You can use browser add-ons for Firefox like Firebug or the Web Developer Toolbar, or you can use a command line tool, or there are places online that you can submit your URL to and they will show the headers returned.

Using the Web Developer Toolbar for Firefox, I get this:

Response Headers - http://fakeplasticfish.com/discuss/



Date: Sun, 01 Nov 2009 21:27:42 GMT

Server: Apache

Keep-Alive: timeout=15, max=99

Connection: Keep-Alive

Transfer-Encoding: chunked

Content-Type: text/html; charset=UTF-8



200 OK

Which is correct, and different from before, and it looks like you fixed it.

[chrishajer]

Yes they should change the documentation, but right now the project is without a leader, so a few things have fallen by the wayside, including documentation.