We use the last option in 3.6 with Radio New Zealand with CSS caching on. It works great.
I had to do some last minutes tweaks yesterday and they were reflected on the front end right away (even though the page was cached the CSS is not - it is cahced locally by the browser).
[quote]what kind of design area do you include into the css file to get the reference to the image?
[right][post=“7203”]<{POST_SNAPBACK}>[/post][/right][/quote]
You don’t need a design area. Just reference the images using the mysource_files/ virtual location and upload those images as associated files of the CSS File asset. You then use the linked_css design area in your Design parsefile to link to the CSS File asset you created.
From v3.6, there is an option on the CSS File asset’s details screen whether or not to cache the file. If you do cache the file, you cannot use any design areas in the CSS parsefile, just the mysource_files/ virtual location.
If you hard code the URL link in either the CSS file or in the main parse file is the performance hit significant rather than by referencing the mysource_files/virtual location?
Actually, hard-coding the URL link is the fastest option for performance, assuming you get the URL correct. Remember that the Live/Public URL is different from a not-Public/not-Live URL.
[quote]Actually, hard-coding the URL link is the fastest option for performance, assuming you get the URL correct. Remember that the Live/Public URL is different from a not-Public/not-Live URL.
[right][post=“7213”]<{POST_SNAPBACK}>[/post][/right][/quote]
Isn’t using the mysource path (which is then rewritten into the cached CSS file) just as fast?
[quote]Isn’t using the mysource path (which is then rewritten into the cached CSS file) just as fast?
[right][post=“7215”]<{POST_SNAPBACK}>[/post][/right][/quote]
Sorry, yes it is – because the cached CSS file then gets a static URL.