At first I thought it was another issue but I've been at this for several hours and I just don't know what's going on.

All I did was copy the starter folder, changed the name, changed the info file name along with the theme name inside the info file.

It would appear that the subtheme will not work unless the name is Fusion Starter. When I change it to the new name, the layout gets messed up and I can tell by looking at the blocks page that something is not right, the regions don't display like they do when the Fusion Starter theme is enabled.

I don't see how the name would such an effect since it's the name of a new subtheme so it should work correctly. But now, I'm not sure anymore, any ideas ?

CommentFileSizeAuthor
#13 Fusion-715616-rename-style-css.patch38.13 KBaquariumtap
#10 715616-rename-css-files-D7.patch153.89 KBaquariumtap

Comments

espirates’s picture

espirates commented

Update: Ok, I think I know what the problem is,
it was driving me crazy. I found it has to do with the fusion-starter-style.css in theme.info.

When changed to style.css the new name does not take effect even if you clear cache.

I looked into the database and did a search for fusion-starter-style and found that the new changes indeed did not take effect and it still displayed the old name. I found this in the menu router table under my new subtheme.

Anyway to fix it so when the stylesheet name change takes effect ? or is style.css not the correct naming convention for fusion theme ?

I looked in the fusion folder and found css/style.css, maybe this is what is getting confused with so I guess I will have to rename the style.css to something else.

Can anyone confirm this ?

Update:Apparently so, the style.css has to be themname-style.css in order for it to work.

jeremycaldwell’s picture

jeremycaldwell commented
Status: Active » Fixed

Hi espirates, there is no special way to go about naming your sub theme CSS file. That CSS file is loaded from your *.info file for your new theme so you can name it whatever you want. Anytime you make changes to your *.info file though be sure to clear your site's cache on the Performance page as it then reloads that file and updates your changes.

Sounds like you created the theme correctly. Copy Fusion Starter to another folder, give the folder a name, then same name for the *.info file. Update the path for the CSS and you should be set.

espirates’s picture

espirates commented

I did clear cache, several times, it would appear that the style sheet must be named theme-style.css, any other way wont' work. I tried style.css that didn't work only when I did theme-style.css did it work. Maybe I need to try it again, it sounds simple just copy the folder rename, etc that's what I did but never worked until I used the dash.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

geerlingguy’s picture

geerlingguy commented
Version: 6.x-1.0-rc1 » 6.x-1.0
Category: support » bug
Status: Closed (fixed) » Active

I had the exact same problem - it was killing me for about 45 minutes (I almost gave up on Fusion and went back to my Zen-ful state ;-), until I read this post.

I would consider this a bug, because a themer should be able to change the stylesheet to style.css (or anything.css) without the theme layout breaking (the styles didn't get loaded).

sociotech’s picture

sociotech commented
Status: Active » Closed (works as designed)

This is not a bug. This is a feature of Drupal itself.

If you name your sub-theme's stylesheet "style.css" you are telling Drupal to replace the style.css file from the Fusion base theme with your own:

http://drupal.org/node/225125 (see the section titled "Overriding inherited style sheets")

geerlingguy’s picture

geerlingguy commented
Status: Closed (works as designed) » Active

I didn't realize the bases theme used style.css for it's main stylesheet... Could that be changed instead, to something like fusion.css instead? (That's what Zen does, and it avoids this issue altogether).

stephthegeek’s picture

stephthegeek commented
Version: 6.x-1.0 » 7.x-1.x-dev
Assigned: Unassigned » aquariumtap
Category: bug » task

Bumping for discussion for D7 version...

aquariumtap’s picture

aquariumtap commented

I agree this is confusing. +1 for renaming style.css in Fusion Core to fusion_style.css. For consistency, I recommend we give all fusion core stylesheets a fusion_ prefix.

aquariumtap’s picture

aquariumtap commented
StatusFileSize
new 715616-rename-css-files-D7.patch153.89 KB

I'm attaching a patch that renames all core Fusion css files to have the fusion- prefix, including the grid files and IE fixes for consistency.

The patch was based on a feature branch I created on my local repository. I've never created a patch this way before, so let me know if worked!

aquariumtap’s picture

aquariumtap commented
Status: Active » Needs review
stephthegeek’s picture

stephthegeek commented
Title: starter subtheme is not working » Rename Fusion Core's style.css -> fusion-style.css to avoid overwriting with subtheme
Status: Needs review » Needs work

We've decided to just rename Fusion Core's CSS main style.css file, to avoid this problem, but not to prefix *all* css files. Needs new patch for this.

aquariumtap’s picture

aquariumtap commented
StatusFileSize
new Fusion-715616-rename-style-css.patch38.13 KB

Revise patch adds fusion- prefix to the following files:

- styles.css
- styles-rtl.css
- typography.css

aquariumtap’s picture

aquariumtap commented
Status: Needs work » Needs review
aquariumtap’s picture

aquariumtap commented
Status: Needs review » Closed (fixed)

Committed this to the DEV branch.