Open ajporterfield opened 10 years ago
This seems like a pretty general setup issue witht he asset pipeline in your production environment. Are you using image_path
/image-url
anywhere else in your Sass?
Also it might make sense to take a look at the app.config.assets.paths
config variable and see if there are any differences between development and production.
Also, maybe this new gem can help in you in finding the issue: https://github.com/schneems/sprockets_better_errors
But all in all, I fear that this is simply a setup issue and that there is nothing that I could fix in the gem.
This is a continuation of an issue I initially brought up at https://github.com/joliss/jquery-ui-rails/issues/58#issuecomment-29900235.
In my local dev environment, this gem (as well as jquery-ui-rails) correctly produces image paths starting with /assets. In production, however, the images start with /images, and aren't being displayed (404s).
Here are some details about my setup.
I'm deploying with AWS' Elastic Beanstalk (Ruby 1.9.3, Rails 3.2.15). EB precompiles assets automatically after pushing changes via Git. I'm only interested in including jquery ui for the datepicker. My current work around for fixing the bad image paths in production is to override SASS variables (see https://github.com/jhilden/jquery-ui-sass-rails/blob/master/app/assets/stylesheets/themes/_jquery.ui.base.css.scss). Here's what my jquery.ui.custom.css.scss looks like that I'm importing.