BuddyPress.org

With IE6, I see buddypress the way I want to see it. Width 800px

With Firefox and Chrome I get a wider screen.

How to make the width 800px regardless of the browser used.

See the other thread on this, but your host is injecting ad code into the loader.php that pulls the stylesheet.

view source on:

http://illdesigned.com/user/barrymadden/wp-content/themes/buddypress-home/css/loader.php

Dear Barrymadden,

Possibly, the problem must be with Godaddy itself

Godaddy offers the worst hosting service on the planet.

Dear Barry,

I took some time to check the two links you have provided.

It works well with IE6, but not with Firefox.

Now, there must be a clue in that.

In the meantime, have you posted a ticket at Godaddy

or followed the suggestion given above by other members?

Another thing is:

You say you are using \”godaddy economy hosting\”

but Godaddy says \”This page is hosted free, courtesy of GoDaddy.com\”.

This is some confusion.

Is your WPMU/BP ensemble in the root directory?

If not, what\’s the name of the folder where it is installed?

I ask this beacuse I can\’t use Firefox\’s \”view page source\” to see http://illdesigned.com .

It\’s a flash page, and I never use any Adobe products.

And… if you make these changes to the BP core files, don’t forget to save them when updating BP.

Oh, and BTW, upgrading to the paid godaddy hosting will most likely fix the ad code injection issue you’re having; but I would concur with the negative comments about godaddy — paid or not — as a host for a buddypress project. You’ll keep running into problems trying to do more advanced stuff on their servers. That’s just not the market that they’re serving.

I’m having the same problem. I just installed BuddyPress 1.0rc2 today, and it’s the first WPMU install for me, and obviously the first BP install as well. I’ve been running WP for over 2 years though, on the same server (different domain), with complete success.

The install seemed to go fine, and I followed the instructions to also use the BP-home theme for the WPMU home page as well (it fails with any of the 4 choices of home page themes).

The site comes up correctly in IE7. In Firefox (3.0.10) and Chrome (2.0.174.0), no CSS gets loaded.

I’m running this on CentOS 5.2, using NginX 0.7.53. WP runs perfectly.

It’s not an “access” problem. Firebug shows that the CSS file is read correctly (and I can see all of the lines in there, so NginX is serving up the CSS). But, for whatever reason, FF and Chrome both decide that it’s not CSS, and just ignore the styles completely (Firebug says that there are no style elements on the page).

Looking at the NginX debug logs, IE takes the css file with an “Accept: */*” and FF takes it with an “Accept: text/css”. Otherwise, I don’t see any obvious differences.

If I code up my own html file, and use the exact same syntax for the css <link> line that BP generates, FF will _correctly_ parse the css file.

The only thing that seems strange in the BP generated code is that the HTML fails the W3C validator for including an “id=_wpnonce” in the hidden search form field _two times_. But, if I remove one of those lines, FF still fails to parse the css.

Here are the links (the site has zero in it at the moment):

http://songsandjingles.com/wordpress-mu/

Here is a link to my “test” html file, which loads the same css file (where I added yellow as the background color in custom.css):

http://songsandjingles.com/wordpress-mu/testme.html

Just to show that the css file is accessible:

http://songsandjingles.com/wordpress-mu/wp-content/themes/buddypress-home/style.css

Any help would be greatly appreciated, thanks in advance!

P.S. The most obvious difference between my tiny HTML file and the generated one is that I have no DOCTYPE or “profile=” in mine…

OK, responding to my own questions, just not to create work for anyone else who ends up here in the future.

I had a bug in my NginX conf file. For all CSS files that were in subdirectories off the root, I was sending those files through PHP rather than just returning them. That caused the Content-Type to be set to “text/html”, rather than “text/css”.

That’s why it worked without a Doctype (quirks mode kicked in), and failed in Firefox and Chrome with the Doctype in.

I’m having the same issue, but I don’t know how to fix it. I see the solution but don’t know how to implement it myself. Is there code I need to change somewhere to fix it?