image_url is undefined method `[]' for nil:NilClass #98
Comments
|
Ugh. it looks like the Sass::Plugin rack adapter is running. |
|
As a work around: |
|
Yes, the workaround, er.. works. Thanks. |
|
I have same problem with sass-rails 3.2.5 |
|
When I invoke |
|
I also get a similar stack trace with 3.2.5 |
|
the problem seems to have to do with requiring or importing regular css files that have image-url in them, which makes sense, those aren't valid css. It's a deceptive error though. It's because the compressor uses scss, but only sets it up with hard coded options and it doesn't use the same defaults. |
|
Uh. How would that work? The issues is that the scss compressor is expecting that to have been handled already. Please don't use sass functions in CSS files ;) Hunt & pecked on my iPhone... Sorry if it's brief! On Apr 17, 2012, at 4:44 PM, Aaron Jensenreply@reply.github.com wrote:
|
|
Excellent question.. not sure how it would work, but it did before I upgraded to the asset pipeline and rails/sass 3.2 shrug I renamed the file to scss and it's all good now. On Tuesday, April 17, 2012 at 5:36 PM, Chris Eppstein wrote:
|
|
You're right guys. It's my fault, I used image-url in plain-css file. |
|
I'm getting the same issue/stack-trace with sass-rails 3.2.5. I've tried the As far as I can tell I'm not using image-url at all in any files: ~/code/satest (master) $ grep image app/assets/* -R
app/assets/stylesheets/base.scss: background-image: none;
app/assets/stylesheets/base.scss: background-image: url(/images/gradient_incorrect.png); }I'm guessing maybe it's pulling in a css file from a plugin or other gem (eg devise). Is it possible to see what file it's processing when it falls over? |
|
My bad - that stack trace turned out to be from precompiled asset file rather than something current. (That will teach me for just looking at it in the browser rather than going back to the filesystem to confirm...) |
|
I'm having the same issue, and it seems to be a combination of this and #94. I have a partial scss file that has some ERB in it to do an iteration through all the themes we have. In order to get around the problem in #94, the file is called _theme_swatches.css.erb. However, this causes me to get the Is there a workaround that I can use for now? |
|
The same here when sprites are generated - Compass/compass-rails#67 |
|
I found a simple workaround |
|
Is this still an issue? |
|
Same as #121. |
|
Yes, still an issue. Is it closed because there is a fix released in rails 4? People will be running 3.2 for some time. |
|
This problem occurs when you use .css file instead of .scss |
Using the 3.2.4 gem, only in production on first query; subsequent queries work fine
The text was updated successfully, but these errors were encountered: