Error Compiling Css Asset Compass
Contents |
Sign rails error compiling css asset in Pricing Blog Support Search GitHub
Heroku Error Compiling Css Asset
This repository Watch 26 Star 607 Fork 242 Compass/compass-rails Code Issues undefined mixin background image 0 Pull requests 2 Projects 0 Pulse Graphs New issue Error compiling CSS asset #28 Closed marcomontes opened compass linear gradient this Issue Mar 22, 2012 · 1 comment Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 1 participant marcomontes commented Mar 22, 2012 Sass::SyntaxError: Undefined mixin 'linear-gradient'. I'm using rails 3.2.2 and: group :assets do gem 'sprockets' gem 'sass-rails' gem 'coffee-rails' gem 'uglifier' gem 'compass-rails' end thx marcomontes commented Mar 22, 2012 Fix: @include background-image(linear-gradient( ... instead of: @include llinear-gradient( ... marcomontes closed this Mar 22, 2012 Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Terms Privacy Security Status Help You can't perform that action at this time. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up rails error compiling css asset up vote 0 down vote favorite I'm using compass, try to import my custom scss file in application.scss and have this error: here my https://github.com/Compass/compass-rails/issues/28 application.scss code: /* * This is a manifest file that'll be compiled into application.css, which will include all the files * listed below. * * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets, * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path. * * You're free to add application-wide styles to this file and they'll appear at the top of the * compiled file, but it's generally better to create http://stackoverflow.com/questions/19224668/rails-error-compiling-css-asset a new file per style scope. * *= require_self *= require_tree */ @import "foundation_and_overrides"; @import "pnp"; if I remove require_tree error message will disappear but my scss file (pnp.scss) will not be loaded to the page css ruby-on-rails sass compass-sass share|improve this question asked Oct 7 '13 at 12:15 maki 1731114 Where is the button mixin located? It seems your pnp file is trying to use it, but it cannot find it. –SombreErmine Oct 7 '13 at 12:21 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote accepted Create a new file called custom.css.scss in app/assets/stylesheets and then use all the imports there @import "foundation_and_overrides"; @import "pnp"; Hope it helps. share|improve this answer answered Oct 7 '13 at 12:34 ajkumar25 3,15131943 add a comment| up vote 0 down vote You're problem may be that require_self is occurring before require_tree. Meaning that pnp styles won't have access to any other style sheets that may be loaded after it (ie, that contain a mix in). To avoid this kind of confusion, I usually keep all imports in one SCSS file and just require that in application.css. # application.css /* *= require normalize *= require base */ # base.scss @import "foundation_and_overrides"; @import "constants"; @import "buttons"; @import "pnp"; share|improve this answer answered Oct 7 '13 at 12:32 Kyle Truscott 9971514 add a comment| Your Answer draft
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/9219061/error-compiling-css-asset more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, https://mattbrictson.com/untangling-the-rails-asset-pipeline-part-4-troubleshooting helping each other. Join them; it only takes a minute: Sign up Error Compiling CSS Asset up vote 6 down vote favorite 2 I have been trying to deploy a Rail 3.1.1 app on CentOS 6 This is error compiling the error I am getting Error Compiling CSS Errno::ENOENT: No Such File or Directory - /var/www/vhosts/MySite/MyAPP/tmp/cache/assets/sprockets%t43t34t34t...t34t-r32r-r23.lock /usr/local/lib/ruby/1.9.1/tempfile.rb:343:in 'rmdir' I appreciate the help. ruby-on-rails css errno share|improve this question asked Feb 9 '12 at 21:27 Steffan Perry 6671714 4 Clean the cache folder and try again. Just empty the tmp/ folder –Nerian Feb 9 '12 at 21:45 add a comment| 2 Answers 2 active oldest votes up vote 21 down vote There were actually 2 problems. error compiling css First the permissions were wrong. and secondly like Nerian said, you have to clear your tmp folder. To set the correct permissions chown apache.root yourapp -R chmod 755 yourapp -R To clear you tmp folder rake tmp:pids:clear rake tmp:sessions:clear rake tmp:sockets:clear rake tmp:cache:clear share|improve this answer answered Feb 15 '12 at 4:18 Steffan Perry 6671714 thanks @Steffan, solved my problem –fengd Dec 13 '12 at 9:53 Why do I not have to do this on my own computer? Is this the only way to solve it? –MichaelScaria Jan 19 '14 at 23:15 add a comment| up vote 0 down vote If you are using an Apache server you simply need to make sure the apache account www-data can make executions in the directory. chown -R www-data:www-data . service apache2 reload share|improve this answer answered Apr 18 '14 at 10:20 TechyTimo 1,80342637 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged ruby-on-rails css errno or ask your own question. asked 4 years ago viewed 7046 times act
unexpected ways. In this final post of our asset pipeline series, we look at common error messages and problems we have encounted, and offer some quicksolutions. You’re reading the last installment of a four-part series on the Rails asset pipeline. The previous entries are Caches and Compass, Production, and Configuration. Table ofContents Help! My production site is completelyunstyled I’ve precompiled, but styles still don’tload My main stylesheet works, but others donot When precompiling, I geterrors I’m trying to compile on-the-flyinstead Pages loadslowly When indoubt… Help! My production site is completelyunstyled In this scenario you deploy to production, load your site and find that the HTML source code is fine, but no CSS is loading at all. Pull up the Webkit console (⌥⌘C in Safari, ⌥⌘J in Chrome) and you see red 404 error messages for each CSS and JavaScript file.Yikes! I made this mistake myself when first experimenting with Rails 3.1. The solution is easy: run this very important command on the productionserver: bundle exec rake assets:precompile This is needed because Rails by default does not generate or serve its CSS assets in production, so you need to compile them beforehand. For further explanation on this topic, read Part 2: Production of thisseries. I’ve precompiled, but styles still don’tload If you’ve precompiled, double-check that compilation actually worked by listing the contents of the public/assets directory of your application on the productionserver: ls -l public/assets You should see compiled and cache-busted versions of all your CSS, JS and image assets. If not, review the output of rake assets:precompile forerrors. Assuming precompilation worked, make sure that you are accessing your application by way of the web server (i.e. Nginx or Apache, usually on port 80). If you haven’t configured the web server yet and are hitting your application directly (i.e. via thin or webrick on port 3000), assets will notwork. If you don’t wish to set up a web server1, or you want to test your Rails application in production before doing so, set the following inproduction.rb: config.serve_static_files=true Check out Part 3: Configuration of this series to go more in-de