search

ndbroadbent / turbo-sprockets-rails3

Speeds up your Rails 3 assets:precompile by only recompiling changed files, and only compiling once to generate all assets
MIT License
975 stars 78 forks source link

Can't compile assets under Rails 3.2.9.rc1 #26

Closed pivotal-chorus closed 11 years ago

pivotal-chorus commented 11 years ago

We get an error: undefined method `compile_path?' for #Sprockets::StaticCompiler:0x2eb09b70

It looks like rails/actionpack/lib/sprockets/static_compiler.rb no longer defines a compile_path? method.

ndbroadbent commented 11 years ago

Right, Rails 3.2.9 has changed a few things in sprockets. I'll fix this ASAP. Thanks for the report!

On Wednesday, 31 October 2012, pivotal-leopold wrote:

We get an error: undefined method `compile_path?' for #Sprockets::StaticCompiler:0x2eb09b70

It looks like rails/actionpack/lib/sprockets/static_compiler.rb no longer defines a compile_path? method.

— Reply to this email directly or view it on GitHubhttps://github.com/ndbroadbent/turbo-sprockets-rails3/issues/26.

ndbroadbent commented 11 years ago

I've started a new minor version number at 0.3.0 to support 3.2.9.rc1 and higher. Thanks!

clutchtutoring commented 11 years ago

I'm getting the same issue. Using:

ruby '1.9.3' gem 'rails', '3.2.12' gem 'asset_sync' gem 'turbo-sprockets-rails3', '0.2.6' (I had to put it down to this because of railties dependencies)

Every time I deploy now I get this error: Preparing app for Rails asset pipeline Running: rake assets:precompile AssetSync: using /tmp/build_br8mhk0oq3q4/config/initializers/asset_sync.rb rake aborted! undefined method `compile_path?' for #Sprockets::StaticCompiler:0x00000004f91a88

I had the turbo sprockets version above 0.3.0 for a while and I think it was never working (since it took a long time each time precompiling). I put it down to 0.2.6 since I'm using Rails 3.2.12, but it's now giving me that trouble.

Not sure what to do to be honest. Any help would be appreciated!

nfriend21 commented 10 years ago

+1