Subthemeing a Subtheme doesn't import the parent's global.css

you are trying to create a subtheme of a subtheme?

Yeah we discussed this yesterday in IRC and I confirmed on a microsite of my own. The conditional stylesheets are loaded for each mq but the global.css is left out of the original stack. Not sure what the inheritance chain is here but it'd be good to track down. Could it be possibly linked to the name just being global.css and not specific to the theme? The two global.css' may be getting crossed.

Just saw that Jake did a great job explaining how to do this in another post. Basically you need to create a starterkit from your subtheme that you can then use to create your new subthemes. http://drupal.org/node/1447700

Marking as duplicated

Resetting this to "active" because I think, this is a real bug (or the documentation is cheating).

I had the same problem, that the global.css of a subtheme of Omega is not being loaded if there is a subtheme of the subtheme.

I wanted to use the Respond theme and because I wanted to change some of the css and not hack the respond theme I decided to make a subtheme of the Respond theme. Because this did not work out of the box I followed http://drupal.org/node/1447700#comment-5638316 accurately and created a starterkit for the respond theme (which is not in the project by default).

But no success: My new theme (respond_my_project) looked awful and I could not recognise that it was Respond at all.

So I got a little deeper into it and found out, that indeed the global.css of the Respond theme was not being loaded in my subtheme.

Then I changed the lines

css[global.css][name] =
css[global.css][description] = 
css[global.css][options][weight] = 

in the respond_my_project.info to

css[respond_my_project_global.css][name] =
css[respond_my_project_global.css][description] = 
css[respond_my_project_global.css][options][weight] = 

And now it worked! Now the global.css of the Respond theme got loaded and my changes in the respond_my_project_global.css got loaded too.

So it seems to me, that only the last global.css is going to be loaded and all other files called global.css are left out (fortunately neither alpha nor omega has a global.css of there own, so that this bug only comes up if you are subtheming a subtheme).

So it seems, that http://drupal.org/node/1436308 is already implemented (;-)

P.S.: I tried this also with the Tej theme: Same result!

This is something that can be addressed in an update to the starterkit but making the edits above to the main theme/subtheme will cause it to break. The starterkit method is the best way of implementing a subtheme of a subtheme until we change over the global.css naming in future subthemes.

Marking as a duplicate of the other issue of making global.css more subtheme specific

can't change version #