Hello,
D7 has a configuration setup to "aggregate and compress css files". (and similarly with js).
Ich did select both switches (CSS, Javascript).
Now the source-code of the site shows me up to five css-files in the header, all same with media="all" and similarily four js-Files.
All ass long string replacing the individual module files.
I expected the configuration to yield just one of those files.
Any idea wether this is ok or erraneous?
Thanks Franz
On 1/27/13 6:02 PM, Franz Iberl wrote:
Hello,
D7 has a configuration setup to "aggregate and compress css files". (and similarly with js).
Ich did select both switches (CSS, Javascript).
Now the source-code of the site shows me up to five css-files in the header, all same with media="all" and similarily four js-Files.
All ass long string replacing the individual module files.
I expected the configuration to yield just one of those files.
Any idea wether this is ok or erraneous?
Thanks Franz
It wouldn't surprise me if the caching code can detect that some files are only conditionally used, and keeps those as a separate file, so that the aggregating doesn't change the operation of the site.
On Sun, Jan 27, 2013 at 7:56 PM, Richard Damon wrote:
On 1/27/13 6:02 PM, Franz Iberl wrote:
Hello,
D7 has a configuration setup to "aggregate and compress css files". (and similarly with js).
Ich did select both switches (CSS, Javascript).
Now the source-code of the site shows me up to five css-files in the header, all same with media="all" and similarily four js-Files.
All ass long string replacing the individual module files.
I expected the configuration to yield just one of those files.
Any idea wether this is ok or erraneous?
Thanks Franz
It wouldn't surprise me if the caching code can detect that some files are only conditionally used, and keeps those as a separate file, so that the aggregating doesn't change the operation of the site.
Maybe because of the performance settings.