I just made the 6.19 update and everything is working fine except one thing: My css file doesn't appear if I enable the optimization css files...

I flush all caches but I don't see my css file in my source code.

If I disable the optimization css files, it works.

The css files optimization was already enabled before I made the upgrade, so I know it was working before...

Is anybody know what is that strange issue?

Comments

roper.’s picture

I flush all caches but I don't see my css file in my source code.

Well yeah, that's because you've enabled optimization which aggregates all/most of the CSS into just a couple files. You won't see your CSS file in the head with optimization enabled.

Is that the only issue, or I'm assuming that there's still a problem with your styles not actually getting applied to the page right..?

pyshgavak’s picture

It's the only issue I got with the update.

My css is not applyed when I hit the optimize css files.

For now, I turned it off, but I'd like to resolve it...

rhartmann’s picture

Same problem here.

The CSS code from style.css disappears when CSS optimization is enabled. So with CSS optimization the theme is broken.

This happened after upgrading from Drupal 6.16 to 6.19. Adding style.css to the .info file did not help.

rhartmann’s picture

Any ideas what causes the problem? In my case a custom theme is affected which was originally written for Drupal 4.x, then adapted to Drupal 5.x and Drupal 6.x. Maybe not perfectly, but it worked until 6.16.

With the Upgrade to 6.19, CSS optimization stopped working.

cedrix’s picture

I have just updated to drupal 6.19 and have the same problem...

roper.’s picture

cedrix’s picture

The non-UTF-8 help is great to implement all the css-files, but if it still does not work then you probably might have problems on pages using panels, ctools, css and css_eminage. The later is causing problems in the current stable release (6.x.1.x).

css_emimage makes css-files from ctools empty (which is wrong).

Solution: Update to css_emimage 6.x.2.x.dev (as of 18th of August 2010) and the problem will be solved.

Took me 12 hours to find this out. ;(

Hope this is helpful and saves some time for others.

Best regards

Cedrix