Forum: Radiant CMS Seperate Stylesheets for IE6 and Mozilla/Firefox

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
75a3319c1219bcd8cb46f7eb02a4868a?d=identicon&s=25 Ben Minton (Guest)
on 2007-07-04 04:20
(Received via mailing list)
Hi All,

I have decided to load 2 seperate stylesheets for Internet Explorer and
Firefox. As you know, the code in RadiantCS by default looks nice and
using Firefox but in IE, is more open. Under old HTML sites, it was easy
add a Javascript in the <head> section to load as required however with
Radiant, that is not so simple.

What is the best solution for this? Locate the specific .rhtml files for
site and edit each to include a Javascript/stylesheet modification or
an entry in each page through Radiant, to load a seperate stylesheet?

Cheers, Ben.
Technical Manager
Four Walls and A Roof
South Brisbane QLD AU
Email -
Web -
Sustainability: Education, Sales and Services
8802b1fa1b53e2197beea9454244f847?d=identicon&s=25 Sean Cribbs (Guest)
on 2007-07-04 04:53
(Received via mailing list)

Is the problem with the administration interface or with content on
your site (the public-facing site)?  It's hard to tell from your

75a3319c1219bcd8cb46f7eb02a4868a?d=identicon&s=25 Ben Minton (Guest)
on 2007-07-04 06:31
(Received via mailing list)
Hi Sean,

Good question: it is the public facing site.
90ceca5a134a66a99e856c0766093c60?d=identicon&s=25 Chris Parrish (Guest)
on 2007-07-04 07:04

I think that I understand your problem (I have a similar situation).
The solution depends on your exact needs:

If EVERY page needs this, then the magic that makes your styles work
goes in your main, site layout -- right in the <head> section as you
mentioned.  Then, if every page uses this layout, every page gets your

If you only need this for a few select pages, then you either create a
custom layout for those pages and apply that layout to the needed pages
or, use a method similar to the one I mention in this post:

As an aside, since I found that I needed a few extra css definitions
ONLY for IE 5 & 6, I used IE proprietary conditional statements (like:
<!--[if lt IE 7]><style type="text/css" media="screen">@import
"/css/default-old-ie.css";</style><![endif]--> )instead of javascript
browser detection.

I'm not a huge fan of IE conditionals normally, but because it was IE
only, this was a very clean way to accomplish my goals.  Had I also
needed a stylesheet to handle Safari bugs (or Opera, etc), I'd have gone
the way of js.  Just a suggestion.

8aeb5ff3546efc726bab713e4e572a40?d=identicon&s=25 Keymone (Guest)
on 2007-07-04 07:55
(Received via mailing list)
btw there are some problems in admin javascripts:

1. when you collapse a tree node it won't expand again
2. in IE pages under tree node are sorted in reverse order.. don't know
yet, maybe
it's some bug of reorder extension..
75a3319c1219bcd8cb46f7eb02a4868a?d=identicon&s=25 Ben Minton (Guest)
on 2007-07-04 08:05
(Received via mailing list)
Hi Chris,

Thanks for the info, these IE/FF issues are site wide, so the <head>
will be the go. Since you mentioned Safari and Opera, I should check the
site against them also.

Cheers, Ben.
This topic is locked and can not be replied to.