Rake Assets:Precompile Throws SASS::Syntaxerror: Invalid CSS After "*/"

rake assets:precompile throws Sass::SyntaxError: Invalid CSS after */

SOLUTION

The file that was breaking things was the font awesome CSS. Removing that from application.css's "require" lines allowed the precompilation to work.

The way to do this was to first delete all of the precompilation require fields, showing that it would compile, and then to slowly add the require fields back to see where it broke.

(Thanks for all those who helped figure this out.)

rake assets:precompile rake aborted! Sass::SyntaxError: Invalid CSS after ...mages/patternbg: expected ), was .png) repeat-x ...

Try adding quotation marks:

background: image-url('themes/base/images/patternbg.png') repeat-x #efefef;

Precompiling assets failing when including boostrap

You can check the syntax of your files by running sass -c app/assets/stylesheets. That might detect the issue for you.

You can also check this github reference #sass

/*
 * 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, or any plugin's
 * vendor/assets/stylesheets directory 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 bottom of the
 * compiled file so the styles you add here take precedence over styles defined in any other CSS/SCSS
 * files in this directory. Styles in this file should be added after the last require_* statement.
 * It is generally better to create a new file per style scope.
 *
 *= require jquery-ui
 *= require prettyPhoto.css
 *= require prettyLoader.css
 *= require prettyPopin.css
 *= require prettyPhoto.css
 *= require sass/main
 *= require sass/master
 *= require sass/ie
 *= require sass/ie8
 *= require sass/buy_now
 *= require sass/ssl_seal
 *= require font-awesome
 *= require_self
*/

Add Primary Key to a table with existing clustered index

There is little or no difference between a PRIMARY KEY and a UNIQUE constraint on non-nullable columns. So if the columns in question are non-nullable then I suggest you do nothing. The main reason to make a candidate key into a primary key is if you have some software (such as a data modelling tool or other development tool) that expects the key to be identified with a PRIMARY KEY constraint.

---

Related Topics