Closed (fixed)
Project:
Omega
Version:
7.x-4.2
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
1 Apr 2014 at 16:58 UTC
Updated:
7 Apr 2014 at 04:32 UTC
Jump to comment: Most recent
Comments
Comment #1
fubhy commentedI personally don't use Susy but Omega itself doesn't do anything about the Gems other than creating a pre-defined Gemfile in your theme folder. Once that's done, Omega is out of that business entirely and it's all about what you do with your theme and what you choose to use for your Sass stack.
A quick look at the Gemfile generated from Omega reveals that it does not lock the Susy version in any way so as Susy 2.0 is stable now it should automatically install Susy 2.0 when you set up a new theme. If you are on an older project that started before Susy 2.0 was out a bundle update should get you up and running on Susy 2.0.
So: Look at your theme's Gemfile, possibly run "bundle update".
Comment #2
caponey commentedcool, will do. and thank you very much!
Comment #3
lakshminp commentedEven if you've got susy 2 installed and have your code written for susy 1, you can get away by doing this:
@import "susyone";Source: Susy docs