Sass::SyntaxError related to active_admin/mixins #214

Closed
andersonbrandon opened this Issue Jun 21, 2011 · 20 comments

Comments

Projects
None yet
@andersonbrandon

Started GET "/assets/active_admin.css" for 127.0.0.1 at 2011-06-21 01:33:07 -0500
Error compiling asset active_admin.css:
Sass::SyntaxError: File to import not found or unreadable: active_admin/mixins.
Load paths:
/Users/brandon/Projects/aa_test
/Users/brandon/.rvm/gems/ruby-1.9.2-p180@rails3.1pre/bundler/gems/active_admin-6d63e36f9f7c/app/assets/stylesheets
(in /Users/brandon/Projects/aa_test/app/assets/stylesheets/active_admin.css.scss)

Latest active_admin, rails 3.1.0.rc4 - possibly related to fixes from #212 - haven't had a chance to track it down or patch it yet, and is probably a simple fix, but it should be documented.

@gregbell

This comment has been minimized.

Show comment Hide comment
@gregbell

gregbell Jun 23, 2011

Contributor

This should be fixed now on the latest rails-3-1 branch.

Contributor

gregbell commented Jun 23, 2011

This should be fixed now on the latest rails-3-1 branch.

@gregbell gregbell closed this Jun 23, 2011

@Godisemo

This comment has been minimized.

Show comment Hide comment
@Godisemo

Godisemo Jul 3, 2011

I have this same issue with latest version both from master and rails-3-1 branches

edit: I'm using rails 3.1.0.rc4

edit 2: This was fixed for me by using the gem sass-rails instread of just sass

Godisemo commented Jul 3, 2011

I have this same issue with latest version both from master and rails-3-1 branches

edit: I'm using rails 3.1.0.rc4

edit 2: This was fixed for me by using the gem sass-rails instread of just sass

@shilov

This comment has been minimized.

Show comment Hide comment
@shilov

shilov Jul 15, 2011

Godisemo's sass-rails suggestion worked for me as well.

shilov commented Jul 15, 2011

Godisemo's sass-rails suggestion worked for me as well.

@camilleroux

This comment has been minimized.

Show comment Hide comment
@camilleroux

camilleroux Aug 11, 2011

'sass-rails' is already present in the group :assets in rails 3.1. What do i have to change ?

'sass-rails' is already present in the group :assets in rails 3.1. What do i have to change ?

@szymon-przybyl

This comment has been minimized.

Show comment Hide comment
@szymon-przybyl

szymon-przybyl Sep 18, 2011

Contributor

I have sass-rails ~> 3.1.0 in Gemfile, active_admin from Github and Rails 3.1.0 and I have the same error

Contributor

szymon-przybyl commented Sep 18, 2011

I have sass-rails ~> 3.1.0 in Gemfile, active_admin from Github and Rails 3.1.0 and I have the same error

@szymon-przybyl

This comment has been minimized.

Show comment Hide comment
@szymon-przybyl

szymon-przybyl Sep 18, 2011

Contributor

in active_admin.css.sass i've changed:

@import "active_admin/mixins";
@import "active_admin/base";

to

@import "active_admin/mixins.css";
@import "active_admin/base.css";

And now that error is gone :)

Contributor

szymon-przybyl commented Sep 18, 2011

in active_admin.css.sass i've changed:

@import "active_admin/mixins";
@import "active_admin/base";

to

@import "active_admin/mixins.css";
@import "active_admin/base.css";

And now that error is gone :)

@szymon-przybyl

This comment has been minimized.

Show comment Hide comment
@szymon-przybyl

szymon-przybyl Sep 19, 2011

Contributor

My bad, it still isn't working, becouse inside activeadmin there are another imports without .css extenstion and i have similar error :/

Contributor

szymon-przybyl commented Sep 19, 2011

My bad, it still isn't working, becouse inside activeadmin there are another imports without .css extenstion and i have similar error :/

@szymon-przybyl

This comment has been minimized.

Show comment Hide comment
@szymon-przybyl

szymon-przybyl Sep 19, 2011

Contributor

Ok, changing that file from scss to sass with .css extenstions for imports fixed it

Contributor

szymon-przybyl commented Sep 19, 2011

Ok, changing that file from scss to sass with .css extenstions for imports fixed it

@szymon-przybyl

This comment has been minimized.

Show comment Hide comment
@szymon-przybyl

szymon-przybyl Sep 19, 2011

Contributor

actually migrating to Rails 3.1.1.rc1 fixed finally all the problems with compiling activeadmin assets, gregbell#490 (comment)

Contributor

szymon-przybyl commented Sep 19, 2011

actually migrating to Rails 3.1.1.rc1 fixed finally all the problems with compiling activeadmin assets, gregbell#490 (comment)

@mspanc

This comment has been minimized.

Show comment Hide comment
@mspanc

mspanc May 4, 2012

Contributor

I can confirm that issue on ActiveAdmin 0.4.3, rails 3.2.3 with heroku

Contributor

mspanc commented May 4, 2012

I can confirm that issue on ActiveAdmin 0.4.3, rails 3.2.3 with heroku

@MSch

This comment has been minimized.

Show comment Hide comment
@MSch

MSch May 11, 2012

Please reopen the issue, I'm having the issue with the latest ActiveAdmin.

MSch commented May 11, 2012

Please reopen the issue, I'm having the issue with the latest ActiveAdmin.

@BlakeWilliams

This comment has been minimized.

Show comment Hide comment
@BlakeWilliams

BlakeWilliams May 12, 2012

Also confirming for ActiveAdmin 0.4.4 with Rails 3.2.2 on Heroku.

Also confirming for ActiveAdmin 0.4.4 with Rails 3.2.2 on Heroku.

@erickreutz

This comment has been minimized.

Show comment Hide comment
@erickreutz

erickreutz May 18, 2012

Same here. ActiveAdmin 0.4.4. with rails 3.2.2 on Heroku.

Same here. ActiveAdmin 0.4.4. with rails 3.2.2 on Heroku.

@bmc

This comment has been minimized.

Show comment Hide comment
@bmc

bmc May 29, 2012

Also occurs on Mac OS X Lion, with Rails 3.2.3, ActiveAdmin 0.4.4, Ruby 1.9.3-p194. Same Rails project works fine on an Ubuntu 11.10 system (with identical software versions). Ruby installed via rvm on both machines.

bmc commented May 29, 2012

Also occurs on Mac OS X Lion, with Rails 3.2.3, ActiveAdmin 0.4.4, Ruby 1.9.3-p194. Same Rails project works fine on an Ubuntu 11.10 system (with identical software versions). Ruby installed via rvm on both machines.

@spilliton

This comment has been minimized.

Show comment Hide comment
@spilliton

spilliton Jun 6, 2012

I was having this issue and then found this: http://stackoverflow.com/questions/7713151/rails-3-1-active-admin-heroku-error-on-first-load-sasssyntaxerror

I moved gem 'sass-rails', "~> 3.2.3" outside of the :assets group in my Gemfile and it fixed the issue, but this doesn't seem right as rails puts it in that group by default...

I was having this issue and then found this: http://stackoverflow.com/questions/7713151/rails-3-1-active-admin-heroku-error-on-first-load-sasssyntaxerror

I moved gem 'sass-rails', "~> 3.2.3" outside of the :assets group in my Gemfile and it fixed the issue, but this doesn't seem right as rails puts it in that group by default...

@pmq20

This comment has been minimized.

Show comment Hide comment
@pmq20

pmq20 Jun 13, 2012

Contributor

@camilleroux move it out from that group worked for me.

Contributor

pmq20 commented Jun 13, 2012

@camilleroux move it out from that group worked for me.

@nathanhinish

This comment has been minimized.

Show comment Hide comment
@nathanhinish

nathanhinish Aug 3, 2012

@spilliton actually the better thing to do here might be to go into config/application.rb and comment out the first Bundler.require line and uncomment the second Bundler.require line. The preceding comment says this...

"If you want your assets lazily compiled in production, use this line"

@spilliton actually the better thing to do here might be to go into config/application.rb and comment out the first Bundler.require line and uncomment the second Bundler.require line. The preceding comment says this...

"If you want your assets lazily compiled in production, use this line"

@spilliton

This comment has been minimized.

Show comment Hide comment
@spilliton

spilliton Aug 28, 2012

@nathanhinish thanks for pointing me toward that, I didn't have that line in my application.rb, but when I searched it came up in some gems.

I reverted my Gemfile to have the requirement in the assets group and added this to the bottom of my application.rb

Bundler.require(:default, :assets, 'development')

Seemed to work :)

@nathanhinish thanks for pointing me toward that, I didn't have that line in my application.rb, but when I searched it came up in some gems.

I reverted my Gemfile to have the requirement in the assets group and added this to the bottom of my application.rb

Bundler.require(:default, :assets, 'development')

Seemed to work :)

@fro

This comment has been minimized.

Show comment Hide comment
@fro

fro Aug 30, 2012

I moved the gem sass-rails outside of the :assets group in my Gemfile and it fixed the issue too.

fro commented Aug 30, 2012

I moved the gem sass-rails outside of the :assets group in my Gemfile and it fixed the issue too.

@jclay

This comment has been minimized.

Show comment Hide comment
@jclay

jclay Oct 1, 2012

Moving sass-rails out of the assets group was the solution for me as well. Thanks for the fix!

jclay commented Oct 1, 2012

Moving sass-rails out of the assets group was the solution for me as well. Thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment