Closed (duplicate)
Project:
Omega
Version:
7.x-4.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
18 Aug 2014 at 11:05 UTC
Updated:
14 Jul 2015 at 23:37 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
steverossnyc commentedI'm having the exact same problem. Anyone out there know which gem is throwing the error?
Comment #2
fubhy commented@see #2259101: @import "toolkit-no-css" generates compile error
Replace @import toolkit/border-box with @import toolkit/kickstart and replace @import toolkit-no-css with @import toolkit.
The "missing breakpoint" error is new. Can't check right now but a quick search @google got me a handful of results. Please try the suggestions in those stackoverflow issues and report back here.
Comment #3
mrpauldriver commentedHi fuhby, great that you are here.
The toolkit suggestions work and copied below are the remaining errors.
I've also posted this issue at http://stackoverflow.com/questions/25361958/sass-compilation-errors-usin...
Perhaps worth mentioning also is that singularitygs 1.3 has now been released and is also being installed.
Comment #4
mrpauldriver commentedComment #5
palagpatski commentedHi, I'm also having the same issues. I've been trying to solve this problem for the past few days with no luck. This is what I get after running
bundle exec guardordrush omega-guardAfter editing sass files this is what I get:
Comment #6
palagpatski commentedThen this is the output on the browser:
Comment #7
rtackett commentedI just resolved this problem. In your gem file and scss @imports, make sure they say only 'toolkit' and not toolkit-no-css or anything else.
In your config.rb, add breakpoint and singularitygs as requirements
Comment #8
palagpatski commentedWow, thanks naptown! This worked for me.
Comment #9
rtackett commentedComment #10
mrpauldriver commented@naptown your suggestions work, thank you. However @import toolkit/border-box in subtheme.normalize.scss does need changing to @import toolkit/kickstart as @fuhby says at #2.
Comment #11
syam.mohan.vs commentedHi
After following instructions in this compilation errors with gems have disappeared (am using 7.x-4.2 not the dev. I manually changed the relevant files). However am still getting errors while guard is trying to access files in the following folders - "variables", "abstractions", "base", "components".
***********
Compilation failed in 2 files.
error sass/layouts/base/base.layout.scss (Line 1 of sass/variables/**/*: File to import not found or unreadable: ../../variables/_colors.scss.
Load paths:
/opt/bitnami/apps/drupal/htdocs/sites/all/themes/t7website/sass
Compass::SpriteImporter
/opt/bitnami/apps/drupal/htdocs/sites/all/themes/t7website/sass
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/compass-core-1.0.1/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/susy-2.1.3/sass
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/compass-normalize-1.5/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/compass-rgbapng-0.2.1/lib/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/toolkit-2.6.0/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/sassy-maps-0.4.0/sass
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/breakpoint-2.5.0/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/singularitygs-1.4.0/stylesheets
Sass::Globbing::Importer)
error sass/layouts/home/home.layout.scss (Line 1 of sass/variables/**/*: File to import not found or unreadable: ../../variables/_colors.scss.
Load paths:
/opt/bitnami/apps/drupal/htdocs/sites/all/themes/t7website/sass
Compass::SpriteImporter
/opt/bitnami/apps/drupal/htdocs/sites/all/themes/t7website/sass
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/compass-core-1.0.1/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/susy-2.1.3/sass
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/compass-normalize-1.5/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/compass-rgbapng-0.2.1/lib/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/toolkit-2.6.0/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/sassy-maps-0.4.0/sass
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/breakpoint-2.5.0/stylesheets
/home/syam/.rvm/gems/ruby-1.9.3-p484@omega.t7website/gems/singularitygs-1.4.0/stylesheets
Sass::Globbing::Importer)
write css/t7website.no-query.css
write css/t7website.normalize.css
write css/t7website.styles.css
Compilation failed in 2 files.
***********
Currently the references to these folders are like this
@import "../../variables/**/*";
@import "../../abstractions/**/*";
@import "../../base/**/*";
@import "../../components/**/*";
Should the format of these be changed as well with the new versions of GEMS installed. Currently my gem.lock file contents are like this
***************************
GEM
remote: https://rubygems.org/
specs:
addressable (2.3.6)
breakpoint (2.5.0)
sass (~> 3.3)
sassy-maps (< 1.0.0)
celluloid (0.15.2)
timers (~> 1.1.0)
chunky_png (1.3.1)
coderay (1.1.0)
compass (1.0.1)
chunky_png (~> 1.2)
compass-core (~> 1.0.1)
compass-import-once (~> 1.0.5)
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
sass (>= 3.3.13, < 3.5)
compass-core (1.0.1)
multi_json (~> 1.0)
sass (>= 3.3.0, < 3.5)
compass-import-once (1.0.5)
sass (>= 3.2, < 3.5)
compass-normalize (1.5)
compass (>= 0.12.0)
compass-rgbapng (0.2.1)
chunky_png (>= 0.8.0)
compass (>= 0.10.0)
compass-validator (3.0.1)
css_parser (1.3.5)
addressable
em-websocket (0.5.1)
eventmachine (>= 0.12.9)
http_parser.rb (~> 0.6.0)
eventmachine (1.0.3)
ffi (1.9.3)
formatador (0.2.5)
guard (2.6.1)
formatador (>= 0.2.4)
listen (~> 2.7)
lumberjack (~> 1.0)
pry (>= 0.9.12)
thor (>= 0.18.1)
guard-compass (1.1.0)
compass (>= 0.10.5)
guard (~> 2.0)
guard-livereload (2.3.0)
em-websocket (~> 0.5)
guard (~> 2.0)
multi_json (~> 1.8)
guard-shell (0.6.1)
guard (>= 1.1.0)
http_parser.rb (0.6.0)
listen (2.7.9)
celluloid (>= 0.15.2)
rb-fsevent (>= 0.9.3)
rb-inotify (>= 0.9)
lumberjack (1.0.9)
method_source (0.8.2)
multi_json (1.10.1)
oily_png (1.1.1)
chunky_png (~> 1.3.0)
pry (0.10.1)
coderay (~> 1.1.0)
method_source (~> 0.8.1)
slop (~> 3.4)
rb-fchange (0.0.6)
ffi
rb-fsevent (0.9.4)
rb-inotify (0.9.5)
ffi (>= 0.5.0)
sass (3.4.1)
sass-globbing (1.1.1)
sass (>= 3.1)
sassy-maps (0.4.0)
sass (~> 3.3)
singularitygs (1.4.0)
breakpoint (~> 2.4)
sass (~> 3.3)
slop (3.6.0)
susy (2.1.3)
sass (>= 3.3.0, < 3.5)
thor (0.19.1)
timers (1.1.0)
toolkit (2.6.0)
sass (~> 3.3)
yajl-ruby (1.2.1)
PLATFORMS
ruby
DEPENDENCIES
breakpoint
compass
compass-normalize
compass-rgbapng
compass-validator
css_parser
guard
guard-compass
guard-livereload
guard-shell
oily_png
rb-fchange
rb-fsevent
rb-inotify (~> 0.9)
sass
sass-globbing
singularitygs
susy
toolkit
yajl-ruby
*****************
Please help.
Comment #12
syam.mohan.vs commentedChanging the issue status.
Comment #13
syam.mohan.vs commentedIt seems the issue is with Sass Globbing V1.1.1. Problem was resolved when I switched back to V1.1.0 (Replaced gem 'sass-globbing' with gem 'sass-globbing', '1.1.2' in Gemfile). There seems to be a fix in the latest version of Sass Globbing V1.1.2 as stated here - http://ruby-doc.org/gems/docs/s/sass-globbing-pr-20-1.1.2/CHANGELOG_mark.... But running bundle shows that it is not yet available for my machine.
Comment #14
bradjones1Making only the edits in #7 and #10 appear to fix this; no need to change your Gemfile.
Does this need a patch?
Comment #15
stred commentedmarked as duplicate of #2328155: Error compilation SASS, the Gemfile.lock file needs to be updated like that one.
Comment #16
sunnykasera3107 commentedI am facing this issue.
I have install all these http://awesomescreenshot.com/0ab3ilqzc1
And config.rb have these all http://awesomescreenshot.com/0be3ilra48
But still I am facing this issue. Please help.
Comment #17
jaylotta commentedFixed after alot of research.
I'm not understanding why this would be happening on a new drupal install with a new install of omega and a new subtheme created with the wizard.
Can anyone explain if this is a problem with Omega or not. Kind of leaves a bad taste in my mouth that the first time I try the theme after reading all of the hype it barfs all over the place. For now I'm sticking with Zen until I stop seeing these kinds of errors.
Comment #18
drupalmani28 commented@MrPaulDriver @naptown Thank you very much guys. Thanks a lot. You are saved my time. #7 and #10 is working for me. :)
Comment #19
mhamed commentedHere I ve got the same problem every time i tried to test a site with omega 4 sub themes:
depending on the circumstances i got the errors like:
or
change many things but so in a hurry perhaps that i could not detect the problem
I solve the problem by copying the files :
Gemfile
Gemfile.lock
config.rb
from the omega base theme within the new one replacing the others
So I omit the error
since t ve seen that the drush exec guard within the omega base theme do not produce the errors
Comment #20
norhusz commentedImporting relative paths ("../../variables/**/*" ,etc.) broken in version 1.1.1 of sass-globbing.
Reverting to 1.1.0 worked for me!
I rewrote the line from sass-globbing (1.1.1) to sass-globbing (1.1.0) in the Gemfile.lock file, then
gem uninstall sass-globbinggem install sass-globbing -v 1.1.0bundle installThe description of the issue on Github
Comment #21
mesnitu commentednorhusz thanks !
Wasted a lot of time to find this solution.
And now I see that the omg sub-theme as a right configuration, so is using sass-globbing (1.1.0)
What a waste of time
Comment #22
basvredelingFree beer for #20!
Comment #23
ngocketit commented#20 works for me. Thanks norhusz!
Comment #24
monstordh commentedI'm finally getting set up with this stuff and have a problem when I begin guarding. This is all new to me. This is my output:
Any suggestions would be appreciated.
UPDATE: I was able to get rid of these warnings by upgrading ruby and all of my gems. However, neither Guard, nor LiveReload are working, even though they are being invoked. Now I'm looking for a solution for this issue.