A beta version of Internet Explorer 7 was just recently released, and with it the ability to autodiscover and read syndicated feeds with just a click of a button (more similar to Apple's Safari than Firefox's Livemarks). Unfortunately, its ability to do this will fail on any RSS feed produced by Drupal 4.6, due to lack of support for XML entity doctype declarations (which Drupal 4.6 includes in its RSS). There's nothing wrong with IE, and there's nothing wrong with Drupal - we're both doing the Right Thing in regards to standards. The complete technical reasoning for all this is available, and won't be a problem in the forthcoming Drupal 4.7. There is, however, a one-line fix to your Drupal 4.6 web site that will make the two play nice together:
In your modules/node.module file, look for this line of code:
$output .= "<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC \"-//W3C//ENTITIES Latin 1 for XHTML//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent\">]>\n";
Delete the entire line - be sure not to change anything else. Once you do that and your Drupal cache naturally expires (if you've enabled the cache, that is), IE7 will be able to autodiscover and, more importantly, parse your Drupal 4.6 feed correctly.
If you're using Drupal 4.6's aggregator, a similar deletion in modules/aggregator.module also needs to be made.
Comments
thanks!
I was just experimenting with IE 7 beta yesterday, encountered the problem with viewing Drupal feeds, and was wondering about this.
Drupal / IE 7
I assume that drupal.org has not implemented this one-liner into their site since I was not able to read this page using IE7 for the above reason (10/20/06). I prefer Firefox but have been considering switching my CMS over to Drupal and want all of my viewers to have the same experience whether or not they use IE7 or Firefox.
Has anyone else implemented this one-liner yet? When does drupal.org plan to have a version running that fixes the issue? I really like what I have to hear about Drupal and am eager to try it out.
Drupal.org is still running
Drupal.org is still running 4.7, not 5.0b1. Generally speaking, d.o doesn't upgrade to the latest release until we get into release candidate mode, which presumes that a number of contrib modules have updated to 5.0, that we're nearly ready to release the full version (and are more than willing to "eat our own dogfood", as it were), etc.
http://www.disobey.com/
http://www.gamegrene.com/
Developer of Drupal's GameAPI
http://www.disobey.com/