By sraborg on

I just upgraded to 6.19 and now my custom theme is not loading CSS properly (or at all). My custom theme is a full on theme (not a subtheme). This was working just fine prior to the upgrade. I can switch to the default themes (garland, etc.) and they work fine, but when I go to mine, styleless... I actually went through the html with firebug and can see that it is not loading the theme's css file.

Things I've done so far:

Switched to a default them and back to mine
Flushed Caches
Ran Update.php
Verify files were not overwritten on the server
Swore a little...

Any help will be most appreciative.

⋅ Categories: Drupal 6.x

Comments

cayenne’s picture

cayenne commented

Turn on css compression if the problem is in Internet Explorer. There is a files limit that really screws things up otherwise.

Oh wait, now I have read your post more carefully. Check to be sure that you have not double installed the theme folder one inside the other. This can screw up paths.

:)

Morten_P_Andersen’s picture

Morten_P_Andersen commented

if you choose Optimize CSS files: Disabled
it works again ???

kaido.toomingas’s picture

kaido.toomingas commented

Also same.. with zen theme
I found this list allso http://www.bxtra.net/Articles/2010-08-12/Drupal-619-and-523-released there is something about css :)

ecmu’s picture

ecmu commented

I had the same problem : only garland theme worked after upgrade to 6.19.

I solved it by desabling "Optimise CSS files" in "Admin | Performance" page.

Now everything is all right.
I hope this will help...

cayenne’s picture

cayenne commented

Does it work in IE?

:)

sraborg’s picture

sraborg commented

Yes it occurs in IE as well.

sraborg’s picture

sraborg commented

Good suggestion. Disabling "Optimize CSS files" followed by flushing the cache does fix the issue. For those who want to know, re-enabling "Optimize CSS files" causes the problem to come back...

heine’s picture

heine commented

This is due to #881132: CSS Optimization breaks with non-UTF-8 .css files.

You can workaround the issue by saving the CSS file as UTF-8 (without a BOM).