I ended up finding this out from a server admin on this issue (see below the line for response). I am trying to contact folks on the SimplePie group about this, but if you all have any ideas that would be helpful as well:

-------------------------------------

OK - this took a bit of debugging to figure out. When the 'SimpleFeed' plugin is enabled, it overrides the 'Content-Type' that is sent to the client. This is bad for CSS on Firefox, as you found. ;)

The problem is in simplepie.inc, in this section:

function handle_content_type($mime = 'text/html') { if (!headers_sent()) { $header = "Content-type: $mime;"; if ($this->get_encoding()) { $header .= ' charset=' . $this->get_encoding(); } else { $header .= ' charset=UTF-8'; } header($header); } }

This will always override the content type to 'text/html'.

I'm really not sure what this section is supposed to do, so I can't recommend a solution unless you want me to really dig into it (which will take significant time).. do you want to check with the author and see what happens?

You can 'prove' this is the issue by simple commenting out '$header = "Content-type: $mime;";'; everything will then work as expected.

-------------------------------------

On Tue, Apr 14, 2009 at 9:58 PM, Jeremy Baron jeremy@tuxmachine.com wrote:

Hi Bobby,

There is definitely a problem with the Content-type generated at your site: http://en.wikipedia.org/w/index.php?title=MediaWiki:Common.css&usemsgcac... yields text/css and <snip>/w/index.php?title=MediaWiki:Common.css&usemsgcache=yes&ctype=text%2Fcss&smaxage=18000&action=raw&maxage=18000 yields text/html

Some stylesheet URLs (which I'm guessing are served directly by the web server, Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8b mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.5) seem to be fine. (like /w/skins/common/shared.css?195)

Can you check your Apache httpd error logs?

I can't dig much more right now, maybe someone else has a suggestion.

Jeremy

On Apr 14, 2009, at 8:42 PM, Bobby S wrote:

<snip> > > I deleted the common.js page because I thought it might be what was > causing the css issue.  If you look at the site on Firefox the css > doesn't load.  If you look at the site on IE or Chrome it does.  Not > sure why this is - really odd. > > Regarding the Feedback widget, I just couldn't get it working so I had > removed the stuff for now.  If you wanted to try I have set up a > username and password for you:

<snip> > > I gave you upgraded status so you can play.  :) > > Bobby > > On Mon, Apr 13, 2009 at 8:41 PM, Jeremy Baron <jeremy@tuxmachine.com> > wrote: >> >> You don't have a staging site I can see?  If you like I can leave the URL >> out of public communications... >> >> Do you have a URL for the CSS issue?  (or is that all mediawiki >> instances?) >>  open the Error Console (tools menu) and clear it then open the page with >> the css issue and see what it says. (make sure it's set to show all >> messages) >> >> Jeremy >> >> On Apr 13, 2009, at 11:10 AM, Bobby S wrote: >>> >>> I know this makes it more difficult, but I would rather not right now >>> - I am launching in two weeks, so I will revisit it then - this is >>> just a refinement, obviously not part of the base product, so I am >>> fine with that.  Thanks so much though!  I will follow up soon. >>> >>> By the way, have you ever had issues with Firefox not loading >>> monobook.css and common.css?  I seem to have that issue, but only in >>> Firefox - even when I click CTRL + F5 it doesn't work. >>> >>> Bobby >>> >>> On Sun, Apr 12, 2009 at 6:02 PM, Jeremy Baron <jeremy@tuxmachine.com> >>> wrote: >>>> >>>> Can I have a link to your wiki to see it myself? >>>> >>>> On Apr 12, 2009, at 5:56 PM, Bobby S wrote: >>>>> >>>>> Jeremy, >>>>> >>>>> Hey - I tried what you wrote re: Get Satisfaction's widget, but what I >>>>> end up with is a text FEEDBACK link at the bottom of each page.  It >>>>> should be a feedback graphic like the one on the right of this page: >>>>> >>>>> http://getsatisfaction.com/widgets >>>>> >>>>> Also, with regard to the capitalization issue - that actually is my >>>>> point, that Fort_wayne_tincaps has never existed, but when you type in >>>>> fort wayne tincaps it goes to Fort Wayne TinCaps.   On my Mediawiki >>>>> install I created a page called "Fort Wayne TinCaps", but when I type >>>>> in "fort wayne tincaps" it says the page doesn't exist - basically I >>>>> would have to set up a redirect. >>>>> >>>>> Bobby >>>>> >>>>> On Sun, Apr 12, 2009 at 2:51 PM, Jeremy Baron <jeremy@tuxmachine.com> >>>>> wrote: >>>>>> >>>>>> I forgot to mention that you'll need to load the script and wait >>>>>> until >>>>>> the >>>>>> JS is finished loading before calling it's functions. >>>>>> >>>>>> So try this: >>>>>> common.css: >>>>>> @import >>>>>> >>>>>> >>>>>> url('http://s3.amazonaws.com/getsatisfaction.com/feedback/feedback.css'); >>>>>> >>>>>> common.js: >>>>>> >>>>>> >>>>>> >>>>>> importScriptURI("http://s3.amazonaws.com/getsatisfaction.com/feedback/feedback.js"); >>>>>> addOnloadHook(function importGSFN(){ >>>>>>  var tab_options = {} >>>>>>  tab_options.placement = "right";  // left, right, bottom, hidden >>>>>>  tab_options.color = "#FFF"; // hex (#FF0000) or color (red) >>>>>> >>>>>> >>>>>> >>>>>>  GSFN.feedback('http://getsatisfaction.com/jetblue/feedback/topics/new?display=overlay&style=idea', >>>>>> tab_options);}); >>>>>> >>>>>> The thing about adding the container still applies with this code. >>>>>> >>>>>> On Apr 12, 2009, at 2:38 PM, Jeremy Baron wrote: >>>>>>> >>>>>>> There's no need to write an extension or modify any php. >>>>>>> >>>>>>> You can accomplish that just by modifying common.js and common.css >>>>>>> ( http://www.mediawiki.org/wiki/Manual:Interface/Common.js , >>>>>>> http://www.mediawiki.org/wiki/Manual:Interface/Common.css ) >>>>>>> >>>>>>> It looks like part of it is just a floating iframe w/ position fixed >>>>>>> + >>>>>>> absolute so it might be fine out of the box but you might end up >>>>>>> having >>>>>>> a >>>>>>> piece placed at an undesirable location. (possibly changing from >>>>>>> page >>>>>>> load >>>>>>> to page load or browser to browser) >>>>>>> >>>>>>> If there are any problems you can use an undocumented feature of >>>>>>> their >>>>>>> JS >>>>>>> (at least not documented at getsatisfaction.com/widgets ): >>>>>>> add this line before GSFN.feedback: tab_options.container = >>>>>>> "mycontainerid"; >>>>>>> add a div somewhere on your site with that id >>>>>>> Then the getsatisfaction html will be placed in that container div >>>>>>> instead >>>>>>> of just document.write'ing.  "mycontainerid" can be whatever you >>>>>>> want >>>>>>> (assuming no conflicts with  Since it's an undocumented feature >>>>>>> there's >>>>>>> no >>>>>>> guarantee that it won't break without notice. >>>>>>> >>>>>>> On Apr 12, 2009, at 1:35 PM, Bobby S wrote: >>>>>>>> >>>>>>>> I am trying to add the Get Satisfaction widget to Mediawiki.  Here >>>>>>>> is >>>>>>>> some sample code: >>>>>>>> >>>>>>>> <style type='text/css'>@import >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> url('http://s3.amazonaws.com/getsatisfaction.com/feedback/feedback.css');</style> >>>>>>>> <script >>>>>>>> >>>>>>>> >>>>>>>> src='http://s3.amazonaws.com/getsatisfaction.com/feedback/feedback.js' >>>>>>>> type='text/javascript'></script> >>>>>>>> <script type="text/javascript" charset="utf-8"> >>>>>>>>  var tab_options = {} >>>>>>>>  tab_options.placement = "right";  // left, right, bottom, hidden >>>>>>>>  tab_options.color = "#FFF"; // hex (#FF0000) or color (red) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>  GSFN.feedback('http://getsatisfaction.com/jetblue/feedback/topics/new?display=overlay&style=idea', >>>>>>>> tab_options); >>>>>>>> </script> >>>>>>>> >>>>>>>> Does anyone know how I could do this?  I assume there are two >>>>>>>> routes >>>>>>>> - >>>>>>>> one directly in Monobook.php and another as an extension.  I'm >>>>>>>> actually surprised there isn't an extension for this, but could >>>>>>>> anyone >>>>>>>> help me out on what to do? >>>>>>>> >>>>>>>> Thanks! >>>>>>>> Bobby