Hello,
I am having the problem discussed there: http://drupal.org/node/708496 but it's not linked to the mentionned module.
Recap: when I check "Optimize CSS files" and load a page, Drupal generates 2 merged CSS files in "sites/default/files/css":
- css_1e70be8f7116edcd032864489eb70c0e.css
- css_42ea02ad21894df7a639c4748da63cb9.css
The problem is that when I view the source of the Drupal page, the page tries to load 2 different CSS files!
The "Optimize CSS files" system was working for a couple of days before this bug appeared in my installation.
I'm using a Zen sub-theme, but I doubt it comes from there since the problem remains after switching back to Garland and clearning caches.
This is a critical problem on my websites, since without this setting I hit the IE-can-handle-a-maximum-of-31-css-files bug, so the site is unusable on that browser.
Comments
Comment #1
tnfno commentedSubscribe, I got the same problem after last upgrade. Also use Zen (sub).
Comment #2
damien tournoud commentedWhat makes you think this is a bug? I guess I'm missing the part where the current behavior is not what you expect.
Comment #3
Blackbird commentedI'm back with more info: the problem definitely doesn't come from Core, it's due to modules. On my installation I have 2 of them that when enabled together trigger this bug: "WSOD" and "Front page". Whenever I disable one of those 2, the optimized CSS files are correctly loaded on the page.
Problem solved in my case: I'll just disable the WSOD module on my staging and prod servers. I guess the this issue can be closed (this bug doesn't concern Core).
About your question Damien, the problem is that the name of the 2 optimized CSS files was not the same between the actual files (located in "sites/default/files/css" on my setup) and the 2 corresponding
tags in the HTML page header.
Comment #4
damien tournoud commentedOk then.