Page 1 of 1
unable to see changes, after updating stylesheet [solved]
Posted: Thu Feb 19, 2009 11:54 am
by gemma
This is my first day using cms so I may just be making a silly mistake. I have made changes to a template 'CSS Menu Top and Two Colums' and can see them when viewing the site, but then moved onto changing a stylesheet 'Layout: Top Menu and Two Columns', but cannot seeĀ the changes.
Any suggestions?
Thanks
Gemma
Re: unable to see changes, after updating stylesheet
Posted: Thu Feb 19, 2009 12:05 pm
by RonnyK
Make sure that you are modifying a stylesheet, that is attached to the template. Do this by clicking the CSS-icon on the right of the template, in Layout -> Templates. The stylesheets that show are attached and will effect the template, after changing.
Ronny
Re: unable to see changes, after updating stylesheet
Posted: Thu Feb 19, 2009 12:21 pm
by gemma
Just checked, and yes it is attached to the template, so I don't thin that thats the problem. Thanks though.
Re: unable to see changes, after updating stylesheet
Posted: Thu Feb 19, 2009 12:36 pm
by RonnyK
Can you post the part of the stylesheet, with the change.... And a link to the site.
Ronny
Re: unable to see changes, after updating stylesheet
Posted: Thu Feb 19, 2009 3:53 pm
by gemma
Hi,
The problem seems to have fixed itself now. When I logged back into my account the changes appear to have happened, I've no idea why. But thank you for your time.
Re: unable to see changes, after updating stylesheet [solved]
Posted: Thu Feb 19, 2009 3:55 pm
by nhaack
sorry for asking such a question, but did you make sure to reload the site including CSS? Often the older version comes from your browser cache. So hitting CTRL+F5 (Windows) instead of a simple reload often does the trick.
BEst
Nils
Re: unable to see changes, after updating stylesheet [solved]
Posted: Fri Feb 20, 2009 12:29 pm
by tinhat
In admin go to Site Admin > Global settings and set the value for...
Maximum amount of time (seconds) stylesheets can be cached in the browser:
This parameter should be set relatively high for static sites, and should be set to 0 for site development