Odd CSS Behaviour

[cdicken]

Any chance of a reply to my earlier questions

Of course - sorry I didn't reply earlier but I don't get to spend as much time on the community as I would like.

1. Putting stylesheets in a folder doesn't work?

It works online, but not in preview.

2. If so, why is this the case?

When previewing, Actinic generally manages to find the CSS file in the subfolders by automatically changing the href value within the <link> tag . What it can't find is all the images referenced in the stylesheet so it often looks a bit crap.

3. if the stylesheets are all placed in the root and linked directly to the imported Dreamweaver design layouts, are you saying it is unnecessary to manually copy them into the DesignPreview folder?

The Dreamweaver stuff is a different issue, but yes - if the css file is in the same folder as the html file used as the source of the registered design, you shouldn't have to copy the css files into the DesignPreviewHTML folder.

[cyberstudios]

This has been a very useful thread, thanks for all the input. I've put the ideas together and find that the following works well:

1. Place all styles into one stylesheet (eg global.css)
2. Put global.css into the main website root
3. Remove any references to styles within actinic.css which occur in global.css (eg p, h1, a, etc) - do this in Actinic/design or else the software will overwrite actinic.css.
4. Link global.css to each page design master
5. Add the ! to force the stylesheet to the top of the list (eg !global.css)

Chris is right, if you do this it isn't necessary to copy !global.css in to the designPreview folder. The only files which then need to be copied in are those within your 'images' folder (I refuse to mix all our graphics in with the site html as well!). How about the next update having an 'images' folder as standard Chris?
Thanks!
Paul - Cyber Studios (UK) Ltd