activescaffold/active_scaffold — comment on commit 686f43c1fbd76224be9b32505ecde6d553a0d26d
File:  line 0
By courtland:

I'm using rails 3.2.1. As far as I know, if the file does not have a
sass or scss extension, it will not be processed as sass. When I first
upgraded to this version of active scaffold, my scaffolds had no
colors at all. This was in development and production mode. Renaming
the file with an scss extension fixed the problem. Also, if someone is
not using sass, using @import defeats the point of the asset pipeline.

I do not have a custom active scaffold colors file yet, as I have
always used an active scaffold overrides css that is in my asset
manifest after active scaffold. Maybe that is the difference?

Are you precompilng assets in production mode?

I will test again, but according to asset pipeline documentation a
sass file should have a sass or scss extension.

On Feb 3, 2012, at 11:52 AM, Sergio Cambra

wrote:

> I have tested, both with *= require active_scaffold and @import active_scaffold and it's working
>
> - with sass, including active_scaffold with "*= require", @import line is in generated file
> - with sass, including active_scaffold with "@import", active_scaffold_colors is included in generated file
>
> I'm using rails 3.2.1, are you using rails 3.1?
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/activescaffold/active_scaffold/commit/686f43c1fbd76224be9b32505ecde6d553a0d26d#commitcomment-930986