Closed transparentech closed 8 years ago
Thanks for bringing this issue to my attention. I can take a look later on this week. It looks like we need to fix something to make our gem compatible with sprocket-rails 3.0.0.
See: https://github.com/rails/sprockets-rails/issues/306#issuecomment-169119377 for possible explanation.
This was fixed! I'm going to release v1.0.0 very soon.
I just ran into this as well. Looking forward to the release.
Update to version 1.0.0, removed my workaround and it works again. Thanks!
I updated my app to rails 4.2.5 which brought in sprockets-rails 3.0.0. Rails.application.assets is now nil by default in production. See this issue:
https://github.com/rails/sprockets-rails/issues/237
This causes sprockets-redirect to throw an "undefined method for nil:NilClass":
My workaround was to set
config.assets.compile = true
inproduction.rb
, but I'm not sure that's the best or most efficient solution. Would be happy for any other workaround suggestions or official solutions.