Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In a D7.14 and Aurora 1.0-rc2 install I get.
error sass/style.scss (Line 20 of sass/partials/global/_base.scss: File to import not found or unreadable: aurora-susy.
Error happened after installing the latest compass aurora gem. I assume its because @import 'aurora-susy'; has been replaced by @import 'aurora/susy-grid'.
I suppose the solution is to upgrade to Aurora 1.1.
Comments
Comment #1
Snugug CreditAttribution: Snugug commentedMoving from the previous gem to the current gem changed the partial structure precisely as you suggested, so how you suggested to solve it is precisely how it's designed to work. That will solve your issue.
Comment #2
mrynearson CreditAttribution: mrynearson commentedThanks. Got everything working with the fix from http://drupal.org/node/1748300 and indeed the solution is to use the updated gem.
Comment #3
davidfells81@gmail.com CreditAttribution: davidfells81@gmail.com commentedAdding
to my config.rb seems to get me past the aurora/susy-grid include failure and onto a failure loading toolkit...
Which is of course, like the other gems, available...
Comment #4
Snugug CreditAttribution: Snugug commentedOkay davidfells, what I'd like you to do is run the following commands and paste me the results:
ruby -v
which ruby
gem list
I'd also like to know what OS you're on, the exact contents of your config.rb file, and how you created your subtheme (did you create it following the instructions provided? If so, what options did you use?). I'd also like you to, now that you aren't in RVM, to go to your themes directory and run
compass create test -r aurora --using aurora/susy
and if that works, go into that folder and try and compile.Comment #5
davidfells81@gmail.com CreditAttribution: davidfells81@gmail.com commentedTheme was created by someone else but following the directions. Trying to create a subtheme gives me the results I'd expect since it can't find any of the gems...
Here's the requested ruby data
OSX Mountain Lion, config.rb:
Comment #6
Snugug CreditAttribution: Snugug commentedDo you use the Aurora gem? Not the compass-aurora gem, but the Aurora gem? There are two Aurora gems in existence, mine which is Compass Aurora, and a four year old auth system for Ruby projects simply called Aurora. It appears as if you have the Auth Aurora installed as well, and because A comes before C, Compass finds that gem first, which is where everything falls apart. If you're not using it, uninstall it (
gem uninstall aurora
) and you should be good to go. If you are using it for something, look into Bundler to manage exactly what gems should be used in your projectComment #7
davidfells81@gmail.com CreditAttribution: davidfells81@gmail.com commentedThanks Snugug, I just came here to post that removing "aurora" and leaving "compass-aurora" fixed the problem. That might be worth noting in the documentation - I'd installed aurora previously before I discovered this theme.
Comment #8
star-szrI'm just looking at an existing Aurora subtheme's config.rb and if
require 'aurora'
is auto-generated somewhere, would it make sense to change that torequire 'compass-aurora'
to prevent this conflict?Comment #9
Snugug CreditAttribution: Snugug commentedIt should never have been `require 'aurora'`, always `require 'compass-aurora'`. Changing this should solve whatever issue your'e having.