Not respecting http_generated_images_path

[mattdwen]

First up, I'm running this via Grunt with grunt-contrib-compass, and I've tested both the master and 2.0 branches.

My config is using a custom http_generated_images_path setting. The images are being generated correctly, in the custom path, but then it falls over with:

Errno::ENOENT on line ["28"] of /Users/mattdwen/.rvm/gems/ruby-2.1.1/gems/compass-0.12.3/lib/compass/sass_extensions/functions/image_size.rb: No such file or directory @ rb_sysopen - /Users/mattdwen/www/Projects/group6.co.nz/app/images/template/sprites-retina-s763d863257.png

It's still trying to reference the original path for the images, and not where the sprite was generated.

If I remove the custom http_generated_images_path setting, then everything works as expected.

[benpearson]

On the subject of using this with grunt-contrib-compass.

I found I had to use the following to stop an extra / being added to the start of the background-image paths eg. background-image: url(/images/sprites/sprites-retina/home-sd71939ea7f.png);

imagesDir: 'images',
generatedImagesPath: 'images',
httpGeneratedImagesPath: 'images'
httpImagesPath: 'images'

Correctly generated path is now background-image: url(images/sprites/sprites-retina/home-sd71939ea7f.png);

The httpImagesPath: 'images' line is needed to fix the same problem with retina backgrounds.

[AdamBrodzinski]

Thanks @benpearson ! 🍻