Upon upgrade to Aurora 3 & update of Gemfile to what's on project homepage, I got errors (I think) due to the use of susy to generate my subtheme, so I added susy and respond-to to the Gemfile. Ran bundle install & then bundle exec compass watch. Now getting the following error:

MacBook-Pro:sandbox_aurora3 skt$ bundle install
Resolving dependencies...
Using addressable (2.3.4) 
Using chunky_png (1.2.8) 
Using fssm (0.2.10) 
Using sass (3.2.8) 
Using compass (0.12.2) 
Using blend-mode (0.0.1) 
Using breakpoint (2.0.5) 
Using bundler (1.3.5) 
Using color-schemer (0.2.3) 
Using compass-normalize (1.4.3) 
Using css_parser (1.3.4) 
Using sassy-buttons (0.1.4) 
Using sassy-strings (0.3.1) 
Using singularitygs (1.0.8) 
Using toolkit (1.0.0) 
Using compass-aurora (3.0.5) 
Using respond-to (2.6) 
Using susy (1.0.8) 
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.
MacBook-Pro:sandbox_aurora3 skt$ bundle exec compass watch
>>> Change detected at 09:07:51 to: style.scss
    error sass/style.scss (Line 2 of _aurora.scss: File to import not found or unreadable: respond-to.
Load paths:
  /Users/skt/Documents/Work/host2/d7theming/sites/all/themes/sandbox_aurora3/sass
  /Library/Ruby/Gems/1.8/gems/compass-0.12.2/frameworks/blueprint/stylesheets
  /Library/Ruby/Gems/1.8/gems/compass-0.12.2/frameworks/compass/stylesheets
  /Library/Ruby/Gems/1.8/gems/breakpoint-2.0.5/stylesheets
  /Library/Ruby/Gems/1.8/gems/singularitygs-1.0.8/stylesheets
  /Library/Ruby/Gems/1.8/gems/blend-mode-0.0.1/stylesheets
  /Library/Ruby/Gems/1.8/gems/color-schemer-0.2.3/stylesheets
  /Library/Ruby/Gems/1.8/gems/toolkit-1.0.0/stylesheets
  /Library/Ruby/Gems/1.8/gems/sassy-buttons-0.1.4/stylesheets
  /Library/Ruby/Gems/1.8/gems/compass-normalize-1.4.3/stylesheets
  /Library/Ruby/Gems/1.8/gems/compass-aurora-3.0.5/stylesheets
  Compass::SpriteImporter)

I looked through previous similar issues and perhaps I need to be using older versions of toolkit and/or respond-to? If so, which version(s)? Thanks.

Comments

jmoughon’s picture

Did you update both your Aurora parent theme and custom subtheme to the 3.0 changes?

Snugug’s picture

Status: Active » Closed (works as designed)

You still have Toolkit 1.0.0 in your Gemfile. As it says on the front page, if you're using a pre-Aurora 3.0 subtheme, you need to use older versions of the gems in your Gemfile. Please refer to the Aurora 2.x Gemfile section of the Using Bundler documentation for a proper pre-Aurora 3.0 gemfile.

skt’s picture

Sorry, been a while -- but this is still an issue for me.

@jmoughon -- Yes, both the parent Aurora theme and custom subtheme have the 3.0 settings. The only change I've made is to add

gem 'susy', '1.0.8'
gem 'respond-to', '2.6'

to my Gemfile.

@snugug -- Actually, I've upgraded to Aurora 3, it's just that I'd still like to use Susy. Is that possible? Is susy incompatible with toolkit 1.0.0? If I use toolkit 0.2.6 will that cause other issues in Aurora 3?

Many thanks.

Snugug’s picture

Toolkit 1.0.0+ comes with Breakpoint 2.0.0+, which is incompatible with the respond-to Compass extension. You should not upgrade your Gemfile to new versions of gems, especially when you know there are backwards incompatibilities. That is the very reason you have the Gemfile there in the first place.

Because of Toolkit's dependency on Breakpoint 2.0.0+, you are unable to use both it and the old respond-to gem. Your choices are either to use the Aurora 2.x Gemfile as laid in the Using Bundler section of the home page, or you need to remove your dependency on respond-to from your Gemfile, your config.rb file, and the import from your Sass file. Breakpoint 2.0.0+ comes with Respond-to. If you already have a project where you have set up Breakpoint/Respond-to with, and are going to use Breakpoint 2.0.0+, be sure to include $breakpoint-legacy-syntax: true;

skt’s picture

Understood -- thank you, @snugug. I'll remove respond-to entirely.

So is susy also incompatible with the gems used in Aurora 3?

Snugug’s picture

Susy itself isn't incompatible, but it's not the best experience available and items such as their at-breakpoint mixin provide a bad UX when compared to Singularity's integration with Breakpoint or when trying to use Breakpoint as well (as they are two different mixins for doing similar things)

skt’s picture

Ok, makes sense -- will switch to singularity. Thanks for the help & for your patience with my basic questions. :)