When using Omega Tools to create a sub-theme of Omega the default CSS files are not being created in the CSS folder.
I assume this is a bug because the video tutorial to manually create a sub-theme shows that they need to be copied and renamed.
When using Omega Tools to create a sub-theme of Omega the default CSS files are not being created in the CSS folder.
I assume this is a bug because the video tutorial to manually create a sub-theme shows that they need to be copied and renamed.
Comments
Comment #1
fubhy commentedThe default CSS files should be created automatically and it works in all the tests that I ran. Can you please provide more information about the steps that you took to create the subtheme so I can try to reproduce that behavior / bug?
Comment #2
Shane Grant commentedI will test it again on my development machine and report back.
Comment #3
firstlut commentedUPDATE: Pay no attention to this comment, except as a cautionary tale. Do not list your CSS files in your .info file.
My subtheme CSS files were created, but other than "global.css" they weren't listed in the .info file.
I about went crazy trying to figure out why my styles weren't taking. Luckily, I'd been mucking about in the .info file yesterday trying to add a jQuery doo-dad, and remembered there was just one CSS file in the list.
Hope this helps.
ETA: This probably also explains why my friend's attempt to export an Omega theme had no effect. He made his subtheme manually (I used Omega Tools), and it over-wrote the references to his CSS files. Maybe?
Comment #4
fubhy commentedThe CSS files don't need to be listed (and shouldn't be listed) in the .info file (if you are refering to YOURTHEME-alpha-BLABLABLA.css that is). I repeat: Don't add those to your .info file!
Comment #5
himerus commented