Thread

I’m new at EE, but pretty sure something weird is going on here. Everything was working fine and all of the sudden the CSS broke in Firefox with the template:  Trendy Blue. It still works in IE 6 for some reason? I cleared my cache in both browsers to make sure that I wasn’t crazy.  This happened when I added Weblog entries to the template.

I made sure the css template was assigned a css stylesheet type in the template prefs also! All the linkage is correct too, example:

{assign_variable:my_weblog="default_site"}
{assign_variable:my_template_group="site"}

<link rel='stylesheet' type='text/css' media='all' href='{stylesheet={my_template_group}/site_css}' />
<style type='text/css' media='screen'>@import "{stylesheet={my_template_group}/site_css}";</style>

I did notice when I made a link to the root, it styled the text properly but did not bring in the graphics.
Example:

<link rel="stylesheet" type="text/css" href="/site.css">

Webpage:  http://www.andrewleger.com

Just a guess but it looks like It’s not taking the

{stylesheet={my_template_group}/site_css}

tag pair for some reason? You can see it on my site above, not work in Firefox, but work in IE. I also made another Weblog site to test the theory and had the same outcome… This time I just used some text styles and it still didn’t work.

Please help,
Andy

Hmmm…I have no idea but that is strange. I viewed source in both Safari and Firefox and the CSS reference looks the same. Plugging in the CSS URL brings up the CSS in both browsers.

Could it be the way you have your template named… site_css.v.1203507711?
I guess I’d try something shorter on a test page just to make sure it’s not choking on that.

In the templates, I have named the CSS: site_css.  EE is adding on to the end of it to make site_css.v.1203507711. It looks like some kind of versioning, But I don’t have anything turned on?

I’m having this same issue.  Has anyone figured out a solution to this?

Hiya,

I’m not too sure what your exact problem is but the site_css.v.120350711 is expected behaviour nowadays as that was added into the system in v1.6.1. I know there was quite a long thread some time back about problems people were having with this but I couldn’t find it with a quick forum search. I’m sure if people want to find it though then they will take longer than I did, in a bit of a hurry at the moment but just thought I would let you know that this is indeed normal as of 1.6.1

Best wishes,

Mark